matplotlib-devel Mailing List for matplotlib

On Tue, Mar 26, 2013 at 9:50 AM, Michael Droettboom <md...@st...> wrote:
> I have tagged and uploaded the tarball for the 1.2.1 final release.
> Thanks to all for their hard work on this!  I think the quality of this
> release is very high.
>
> http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.2.1/matplotlib-1.2.1.tar.gz/download
>
> Once the binaries have been posted and the website download links have
> been updated, I'll make a formal announcement in the usual channels.
>
> Mike

Thanks, Mike, for your hard work and perseverance.

As usual Russell, let me know if you have build issues on the Mac.

Happy Tuesday everybody.
Best wishes,
Damon

-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

On 03/26/2013 11:18 AM, Michael Droettboom wrote:
> On 03/26/2013 10:57 AM, Damon McDougall wrote:
>> On Tue, Mar 26, 2013 at 8:25 AM, Benjamin Root <ben...@ou...> wrote:
>>> On Fri, Mar 22, 2013 at 12:35 PM, Michael Droettboom <md...@st...>
>>> wrote:
>>>> I'm hoping to host a matplotlib sprint during the final two days of 
>>>> Scipy
>>>> 2013 this year, and I hope to see as many as possible of you 
>>>> there.  I think
>>>> it's also really important to bring new developers into sprints, 
>>>> because
>>>> it's such an efficient way to get people familiar with the code base.
>>>>
>>>> It might be helpful to start brainstorming now about which projects 
>>>> we may
>>>> want to tackle so that we can have as much in place as possible by 
>>>> then and
>>>> hit the ground running.
>>>>
>>>> I've set up a wiki page here:
>>>>
>>>> https://github.com/matplotlib/matplotlib/wiki/Scipy-2013
>>>>
>>> Getting a bit back on the original topic of the SciPy sprints, there 
>>> are
>>> some things I have learned from last year's sprints.  First off, 
>>> there are
>>> going to be a lot of newbies there who do not even have a developer 
>>> setup,
>>> let alone a source install of matplotlib.  Myself and a few other 
>>> people
>>> spent several hours fumbling around with getting the Mac users set up
>>> properly.  With me not being a Mac user, I felt very helpless.  We 
>>> need to
>>> be better prepared for these users (as well as the Windows users).
>>>
>>> Second, working on matplotlib isn't very "sexy" (at least, insofar as
>>> working on ipython, or one of the scikits).  Most of the attendees are
>>> specialized scientists who only cares enough about matplotlib to 
>>> produce
>>> "the plot" for their work.  Getting attendees to join your sprint is 
>>> a hard
>>> sell.  This is not meant to discourage you, but rather to help 
>>> better frame
>>> what the tasks and goals should be for matplotlib at the sprints.
>>>
>>> I wish I was this prepared last year.  You are off to a much better 
>>> start
>>> than I was.
>>>
>>> Cheers!
>>> Ben Root
>> Ben,
>>
>> This is incredibly useful information.  I have never been to a sprint
>> before so this valuable knowledge to have.  Since I'm a mac user,
>> perhaps I could put together a 'source install walkthrough' or
>> something?  That might help us save some time fumbling at the
>> beginning of the sprint.
>>
> Damon -- I think that would be very helpful.  I can do the same for 
> major Linux distros.  Sadly,Windows is much more complex and I'm not 
> even terribly up on current best practices there.  Any volunteers?
Also -- should we set up a shared place (either a git repo or just a 
wiki page) to collaborate on any of these materials?

Mike

On 03/26/2013 10:57 AM, Damon McDougall wrote:
> On Tue, Mar 26, 2013 at 8:25 AM, Benjamin Root <ben...@ou...> wrote:
>> On Fri, Mar 22, 2013 at 12:35 PM, Michael Droettboom <md...@st...>
>> wrote:
>>> I'm hoping to host a matplotlib sprint during the final two days of Scipy
>>> 2013 this year, and I hope to see as many as possible of you there.  I think
>>> it's also really important to bring new developers into sprints, because
>>> it's such an efficient way to get people familiar with the code base.
>>>
>>> It might be helpful to start brainstorming now about which projects we may
>>> want to tackle so that we can have as much in place as possible by then and
>>> hit the ground running.
>>>
>>> I've set up a wiki page here:
>>>
>>> https://github.com/matplotlib/matplotlib/wiki/Scipy-2013
>>>
>> Getting a bit back on the original topic of the SciPy sprints, there are
>> some things I have learned from last year's sprints.  First off, there are
>> going to be a lot of newbies there who do not even have a developer setup,
>> let alone a source install of matplotlib.  Myself and a few other people
>> spent several hours fumbling around with getting the Mac users set up
>> properly.  With me not being a Mac user, I felt very helpless.  We need to
>> be better prepared for these users (as well as the Windows users).
>>
>> Second, working on matplotlib isn't very "sexy" (at least, insofar as
>> working on ipython, or one of the scikits).  Most of the attendees are
>> specialized scientists who only cares enough about matplotlib to produce
>> "the plot" for their work.  Getting attendees to join your sprint is a hard
>> sell.  This is not meant to discourage you, but rather to help better frame
>> what the tasks and goals should be for matplotlib at the sprints.
>>
>> I wish I was this prepared last year.  You are off to a much better start
>> than I was.
>>
>> Cheers!
>> Ben Root
> Ben,
>
> This is incredibly useful information.  I have never been to a sprint
> before so this valuable knowledge to have.  Since I'm a mac user,
> perhaps I could put together a 'source install walkthrough' or
> something?  That might help us save some time fumbling at the
> beginning of the sprint.
>
Damon -- I think that would be very helpful.  I can do the same for 
major Linux distros.  Sadly,Windows is much more complex and I'm not 
even terribly up on current best practices there.  Any volunteers?

Mike

I have tagged and uploaded the tarball for the 1.2.1 final release. 
Thanks to all for their hard work on this!  I think the quality of this 
release is very high.

http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.2.1/matplotlib-1.2.1.tar.gz/download

Once the binaries have been posted and the website download links have 
been updated, I'll make a formal announcement in the usual channels.

Mike

On Tue, Mar 26, 2013 at 8:25 AM, Benjamin Root <ben...@ou...> wrote:
>
> On Fri, Mar 22, 2013 at 12:35 PM, Michael Droettboom <md...@st...>
> wrote:
>>
>> I'm hoping to host a matplotlib sprint during the final two days of Scipy
>> 2013 this year, and I hope to see as many as possible of you there.  I think
>> it's also really important to bring new developers into sprints, because
>> it's such an efficient way to get people familiar with the code base.
>>
>> It might be helpful to start brainstorming now about which projects we may
>> want to tackle so that we can have as much in place as possible by then and
>> hit the ground running.
>>
>> I've set up a wiki page here:
>>
>> https://github.com/matplotlib/matplotlib/wiki/Scipy-2013
>>
>
> Getting a bit back on the original topic of the SciPy sprints, there are
> some things I have learned from last year's sprints.  First off, there are
> going to be a lot of newbies there who do not even have a developer setup,
> let alone a source install of matplotlib.  Myself and a few other people
> spent several hours fumbling around with getting the Mac users set up
> properly.  With me not being a Mac user, I felt very helpless.  We need to
> be better prepared for these users (as well as the Windows users).
>
> Second, working on matplotlib isn't very "sexy" (at least, insofar as
> working on ipython, or one of the scikits).  Most of the attendees are
> specialized scientists who only cares enough about matplotlib to produce
> "the plot" for their work.  Getting attendees to join your sprint is a hard
> sell.  This is not meant to discourage you, but rather to help better frame
> what the tasks and goals should be for matplotlib at the sprints.
>
> I wish I was this prepared last year.  You are off to a much better start
> than I was.
>
> Cheers!
> Ben Root

Ben,

This is incredibly useful information.  I have never been to a sprint
before so this valuable knowledge to have.  Since I'm a mac user,
perhaps I could put together a 'source install walkthrough' or
something?  That might help us save some time fumbling at the
beginning of the sprint.

-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

On Fri, Mar 22, 2013 at 12:35 PM, Michael Droettboom <md...@st...>wrote:

>  I'm hoping to host a matplotlib sprint during the final two days of Scipy
> 2013 this year, and I hope to see as many as possible of you there.  I
> think it's also really important to bring new developers into sprints,
> because it's such an efficient way to get people familiar with the code
> base.
>
> It might be helpful to start brainstorming now about which projects we may
> want to tackle so that we can have as much in place as possible by then and
> hit the ground running.
>
> I've set up a wiki page here:
>
> https://github.com/matplotlib/matplotlib/wiki/Scipy-2013
>
>
Getting a bit back on the original topic of the SciPy sprints, there are
some things I have learned from last year's sprints.  First off, there are
going to be a lot of newbies there who do not even have a developer setup,
let alone a source install of matplotlib.  Myself and a few other people
spent several hours fumbling around with getting the Mac users set up
properly.  With me not being a Mac user, I felt very helpless.  We need to
be better prepared for these users (as well as the Windows users).

Second, working on matplotlib isn't very "sexy" (at least, insofar as
working on ipython, or one of the scikits).  Most of the attendees are
specialized scientists who only cares enough about matplotlib to produce
"the plot" for their work.  Getting attendees to join your sprint is a hard
sell.  This is not meant to discourage you, but rather to help better frame
what the tasks and goals should be for matplotlib at the sprints.

I wish I was this prepared last year.  You are off to a much better start
than I was.

Cheers!
Ben Root

Benjamin Root writes:
 > On Mon, Mar 25, 2013 at 12:46 PM, Phil Elson <pel...@gm...> wrote:
 > 
 >     >I am putting together a beginners tutorial proposal that I will submit
 >     soon
 >    
 >     That's great to hear! Are you planning on making the tutorial material
 >     part of mpl's docs or using the content that is already out there?
 > 
 > It is all new stuff, but I have been taking inspirations from other tutorials
 > I have seen and said to myself "You are all teaching it wrong!"  :-P
 > 
 > I am ignoring pylab (risky, I know), starting with a *very* basic NumPy
 > primer, and then moving on to teach matplotlib from the perspective of "here
 > are what the parts of a plot are called and what they are for, and see what
 > happens when we put those parts together".  It is an ingredients approach,
 > essentially.

Just for the record: over the last few years I have assembled a
document which is more a collection of facts and tricks on
Numpy/Scipy/Matplotlib which seems orthogonal to your goals.  I am
trying to get students in numerical analysis or similar courses
operational as quickly as possible.  So I am taking pylab as a
baseline.  (So really a Matlab replacement, although most students
will not have had any close contact with Matlab...)

Any comments are welcome.  Some more nice matplotlib examples are on
my wish list, but I have not found time yet...

PDF: http://math.jacobs-university.de/oliver/teaching/numpy-intro/numpy-intro.pdf
HTML: http://math.jacobs-university.de/oliver/teaching/numpy-intro/numpy-intro/index.html
Sources: http://math.jacobs-university.de/oliver/teaching/numpy-intro/

I have been argued back and forth with myself whether I should make it
more pythonic (as most of the "official" matplotlib examples are), but
then on the ground where class time is precious, I came to appreciate
the simplicity of pylab-style code.

Regards,
Marcel


---------------------------------------------------------------------
Marcel Oliver                                 Phone: +49-421-200-3212       
School of Engineering and Science               Fax: +49-421-200-3103
Jacobs University                       m.o...@ja...
Campus Ring 1                                   ol...@me... 
28759 Bremen, Germany         http://math.jacobs-university.de/oliver
---------------------------------------------------------------------