matplotlib-devel — matplotlib developers

[matplotlib-devel] Colored lines and examples / documentation

[David P. S. <dps...@gm...>]

Hi,

It was great to meet many of the Matplotlib developers at SciPy 2013. I had
a great time and I learnt a huge amount, which I am slowly starting to
digest.

In particular, without the Matplotlib sprint, I would never have got off
the ground -- many thanks to all those who took the time to be patient with
me!

I have been working, as a first step, on colored line support. This is not,
of course, new -- it's all in LineCollection. However, as a user,
LineCollection is intimidating and difficult to understand, and does not
lead to easy experimentation (I speak from experience).

At Tony's suggestion, the first step was to rewrite the
multicolored_line.py example.
You can find my first attempt as an IPython notebook at

https://github.com/dpsanders/matplotlib-examples/blob/master/linecolor.ipynb

or

http://nbviewer.ipython.org/urls/raw.github.com/dpsanders/matplotlib-examples/master/linecolor.ipynb

Please let me have any comments before I attempt the next step of making a
pull request.
It seems to me that IPython notebooks are quite a natural format for such
examples, especially with a view to having interactive examples in the
future.

I have tried, as discussed in the sprint, to separate the data processing
from the plotting.
The function "linecolor" (the only other reasonable name that I thought of
was "colorline") should be able to be extracted without too much effort
(hopefully?) into the axes module and into pyplot.

What is the situation with tagging the examples? If the examples are being
refactored, it would seem to at least be a natural moment to start adding
tags, even if nothing is actually done with them yet.


Along these lines, it seems to me that there is a lot of other
functionality which is difficult to get at for the average user who does
not understand collections or patches.

For example, there is an 'arrow' function in pyplot, which just exposes the
FancyArrow patch, but there is no corresponding 'circle', 'ellipse' etc.
function for those patches.
I think this would be a great addition -- what is the general consensus?

By the way, I only understood what an 'axes' object is yesterday, even
though I have been using Matplotlib for several years. The documentation
that I found seems to assume that the user is coming from Matlab and
already implicitly understands what 'axes' refers to.


Some more general comments which I have been led to in this process:

- Ben made the comment that it was very important to have figures in the
documentation for each function. I completely agree with this. It seems to
me that a simple way to achieve this would be to have one example for each
function, with the name of the example file being the same as the name of
the function (à la Matlab!) Thus I have (re-)named the script as
"linecolor.py".

- At the moment, there seem to be too many places with examples:
screenshots, examples, gallery, scipy cookbook, figures for each function,
etc.
I think that the (refactored) gallery is the solution, and is where people
should be pointed -- the screenshots page and the examples page do not seem
to me to be useful / necessary.

- Also during the BoF / sprint, style sheets were discussed several times.
Tony seems to have already solved this problem in his mpltools package -- I
would suggest that this could be brought straight into Matplotlib?

Thanks to everybody for a great package (and for reading all this, if you
get this far). Please let me know if this is (not) the right place to
discuss such things.

Best wishes,
David.



-- 
**************************************************************************
Dr. David P. Sanders

Profesor Titular A / Associate Professor
Departamento de Física, Facultad de Ciencias
Universidad Nacional Autónoma de México (UNAM)

dps...@gm...
http://sistemas.fciencias.unam.mx/~dsanders

Cubículo / office: #414
Tel.: +52 55 5622 4965

Re: [matplotlib-devel] NavigationToolbar2TkAgg changes in v1.2.0 win32 py2.6?

[Brasier, S. <Ste...@at...>]

Ah ok that makes more sense, thanks!



So the change was made in c887139224<https://github.com/matplotlib/matplotlib/commit/c887139224ac30ceb2c77d249acf80da8ac9713e> "Backend factorisation for tooltip sharing".



Is there a reason backends can't provide access to the buttons from the toolbar object somehow though? The use-case is that GUIs using the Figure window can modify the buttons actions, e.g. to have the "save" button save various versions of a plot.



I don't think the means needs to be back-end agnostic, if you're mucking about with GUIs you've already accepted you are tied to a particular one.



Steve

________________________________
This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding.

The ultimate parent company of the Atkins Group is WS Atkins plc. Registered in England No. 1885586. Registered Office Woodcote Grove, Ashley Road, Epsom, Surrey KT18 5BW. A list of wholly owned Atkins Group companies registered in the United Kingdom and locations around the world can be found at http://www.atkinsglobal.com/site-services/group-company-registration-details

Consider the environment. Please don't print this e-mail unless you really need to.

Re: [matplotlib-devel] NavigationToolbar2TkAgg changes in v1.2.0 win32 py2.6?

[Thomas K. <th...@kl...>]

On 4 July 2013 13:27, Brasier, Steve <Ste...@at...> wrote:

> When I look in the svn browser here<http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/lib/matplotlib/backends/backend_tkagg.py?annotate=8989>(which I assume is the current code?)
>
With no updates for the last couple of years? Try here:
https://github.com/matplotlib/matplotlib ;-)

Thomas

[matplotlib-devel] NavigationToolbar2TkAgg changes in v1.2.0 win32 py2.6?

[Brasier, S. <Ste...@at...>]

Hi, I'm wondering if there's something wrong with the source included in the v1.2.0 win32 py2.6 exe?  However I suspect I may have misunderstood something w.r.t svn.

The short version is that some code using the TkAgg backend which used self.figure.canvas.manager.toolbar.bsave stopped working when I upgraded from v1.1.

When I look in the svn browser here<http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/lib/matplotlib/backends/backend_tkagg.py?annotate=8989> (which I assume is the current code?) I can see that in class NavigationToolbar2TkAgg, _init_toolbar() does create self.bsave etc.

However in the source I have from the download here<https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.2.0/matplotlib-1.2.0.win32-py2.6.exe>, _init_toolbar() is a lot shorter and doesn't store the buttons as instance attributes.

Have I got confused or is something out of sync?

Thanks

Steve


________________________________
This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding.

The ultimate parent company of the Atkins Group is WS Atkins plc. Registered in England No. 1885586. Registered Office Woodcote Grove, Ashley Road, Epsom, Surrey KT18 5BW. A list of wholly owned Atkins Group companies registered in the United Kingdom and locations around the world can be found at http://www.atkinsglobal.com/site-services/group-company-registration-details

Consider the environment. Please don't print this e-mail unless you really need to.

Re: [matplotlib-devel] [Numpy-discussion] matplotlib user survey 2013

[Damon M. <dam...@gm...>]

On Wed, Jul 3, 2013 at 3:13 PM, Derek Homeier <
de...@as...> wrote:

>
> On 03.07.2013, at 10:03PM, Damon McDougall <dam...@gm...>
> wrote:
>
> > On Tue, Jul 2, 2013 at 11:39 AM, Michael Droettboom <md...@st...>
> wrote:
> > [Apologies for cross-posting]
> >
> > The matplotlib developers want to hear from you!
> >
> > We are conducting a user survey to determine how and where matplotlib is
> being used in order to focus its further development.
> >
> > This should only take a couple of minutes.  To fill it out, visit:
> >
> >
> https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ
> >
> > Please forward to your colleagues, particularly those who don't read
> these mailing lists.
> >
> > The question, "You *primarily* use matplotlib for..." informs me to
> "check all that apply", but the answers are radio buttons, not check boxes.
> >
> > I'm not sure I have rights to change it.
> >
> But you really only can use it for one thing primarily, right? The "check
> all that apply" seems out of place here.
>

Alright.  That works too.  Thanks :)

-- 
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

Re: [matplotlib-devel] [Numpy-discussion] matplotlib user survey 2013

[Derek H. <de...@as...>]

On 03.07.2013, at 10:03PM, Damon McDougall <dam...@gm...> wrote:

> On Tue, Jul 2, 2013 at 11:39 AM, Michael Droettboom <md...@st...> wrote:
> [Apologies for cross-posting]
> 
> The matplotlib developers want to hear from you!
> 
> We are conducting a user survey to determine how and where matplotlib is being used in order to focus its further development.
> 
> This should only take a couple of minutes.  To fill it out, visit:
> 
> https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ
> 
> Please forward to your colleagues, particularly those who don't read these mailing lists.
> 
> The question, "You *primarily* use matplotlib for..." informs me to "check all that apply", but the answers are radio buttons, not check boxes.
> 
> I'm not sure I have rights to change it.
>  
But you really only can use it for one thing primarily, right? The "check all that apply" seems out of place here.

Cheers,
					Derek
--
----------------------------------------------------------------
Derek Homeier          Centre de Recherche Astrophysique de Lyon
ENS Lyon                                      46, Allée d'Italie
69364 Lyon Cedex 07, France                       +33 47272-8894
----------------------------------------------------------------

Re: [matplotlib-devel] [Numpy-discussion] matplotlib user survey 2013

[Damon M. <dam...@gm...>]

On Tue, Jul 2, 2013 at 11:39 AM, Michael Droettboom <md...@st...> wrote:

>  [Apologies for cross-posting]
>
> The matplotlib developers want to hear from you!
>
> We are conducting a user survey to determine how and where matplotlib is
> being used in order to focus its further development.
>
> This should only take a couple of minutes.  To fill it out, visit:
>
> https://docs.google.com/**spreadsheet/viewform?**fromEmail=true&formkey=**
> dHpQS25pcTZIRWdqX0pNckNSU01sMH**c6MQ<https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ>
>
> Please forward to your colleagues, particularly those who don't read these
> mailing lists.
>

The question, "You *primarily* use matplotlib for..." informs me to "check
all that apply", but the answers are radio buttons, not check boxes.

I'm not sure I have rights to change it.


>
> Cheers,
> Michael Droettboom, and the matplotlib team
>
> _______________________________________________
> NumPy-Discussion mailing list
> Num...@sc...
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>


-- 
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

Re: [matplotlib-devel] Updating copyright model in license

[Michael D. <md...@st...>]

On 07/02/2013 07:51 PM, Nathaniel Smith wrote:
> On Tue, Jul 2, 2013 at 8:31 PM, Michael Droettboom <md...@st...> wrote:
>> As many of you are well aware, John Hunter has been the sole copyright
>> holder on matplotlib from the beginning.  I'm sorry it's taken nearly a year
>> to do this (as can often happen in sad situations like this), but I think we
>> do need to address it going forward.
>>
>> I have a PR for this change in #2195.
>>
>> Heavily influenced by the IPython licensing, I propose to move us to a
>> shared copyright model, where authors retain copyright on their individual
>> contributions, but the code base as a whole belongs to the entire community
>> of contributors.
> Purely as a legal matter, I believe that what you mean is, you're
> suggesting updating the documentation in the source files to more
> accurately reflect the current model? Unless everyone's been signing
> written documents transferring their copyright (which is the only
> effective way to transfer copyright in the US and AFAIK most other
> jurisdictions), then right now matplotlib's copyright is owned by the
> community of contributors, and has been so long as there have been
> contributors.
>
IANAL, but I assumed as much.  The real problem I'm trying to resolve is 
that the explicitly specified copyright (whether it applies or not) is 
still John Hunter.

IPython changed from explicitly listing individuals in their copyright 
line to referring to the IPython community fairly recently, and 
obviously under different circumstances.  Fernando -- was there a 
particular impetus for that or model you were following?

Mike

Re: [matplotlib-devel] Updating copyright model in license

[Nathaniel S. <nj...@po...>]

On Tue, Jul 2, 2013 at 8:31 PM, Michael Droettboom <md...@st...> wrote:
> As many of you are well aware, John Hunter has been the sole copyright
> holder on matplotlib from the beginning.  I'm sorry it's taken nearly a year
> to do this (as can often happen in sad situations like this), but I think we
> do need to address it going forward.
>
> I have a PR for this change in #2195.
>
> Heavily influenced by the IPython licensing, I propose to move us to a
> shared copyright model, where authors retain copyright on their individual
> contributions, but the code base as a whole belongs to the entire community
> of contributors.

Purely as a legal matter, I believe that what you mean is, you're
suggesting updating the documentation in the source files to more
accurately reflect the current model? Unless everyone's been signing
written documents transferring their copyright (which is the only
effective way to transfer copyright in the US and AFAIK most other
jurisdictions), then right now matplotlib's copyright is owned by the
community of contributors, and has been so long as there have been
contributors.

-n

Re: [matplotlib-devel] Updating copyright model in license

[Fernando P. <fpe...@gm...>]

On Tue, Jul 2, 2013 at 12:31 PM, Michael Droettboom <md...@st...> wrote:
> As many of you are well aware, John Hunter has been the sole copyright
> holder on matplotlib from the beginning.  I'm sorry it's taken nearly a year
> to do this (as can often happen in sad situations like this), but I think we
> do need to address it going forward.
>
> I have a PR for this change in #2195.
>
> Heavily influenced by the IPython licensing, I propose to move us to a
> shared copyright model, where authors retain copyright on their individual
> contributions, but the code base as a whole belongs to the entire community
> of contributors. This does not actually change the license from the BSD one
> that we have had all along, so should have no impact on its usability in or
> with other projects.  I feel pretty strongly that this is the right
> direction, as it reflects that matplotlib was and is a community project.
> (And just to be clear, this is in no way an attempt to reduce John's credit
> for the amazing work that he began).

+1

Not that I have any right to speak for him, but I suspect/imagine that
he would have been totally on board with this plan, and I wouldn't be
surprised if the fact that it hadn't happened before wasn't simply an
oversight.

Very happy to see you take this step, I think it's the right approach.

Cheers,

f

[matplotlib-devel] Updating copyright model in license

[Michael D. <md...@st...>]

As many of you are well aware, John Hunter has been the sole copyright 
holder on matplotlib from the beginning.  I'm sorry it's taken nearly a 
year to do this (as can often happen in sad situations like this), but I 
think we do need to address it going forward.

I have a PR for this change in #2195.

Heavily influenced by the IPython licensing, I propose to move us to a 
shared copyright model, where authors retain copyright on their 
individual contributions, but the code base as a whole belongs to the 
entire community of contributors. This does not actually change the 
license from the BSD one that we have had all along, so should have no 
impact on its usability in or with other projects.  I feel pretty 
strongly that this is the right direction, as it reflects that 
matplotlib was and is a community project.  (And just to be clear, this 
is in no way an attempt to reduce John's credit for the amazing work 
that he began).

I hope this will be noncontroversial, but I'm always wary of starting 
legal discussions on a mailing list.

Mike

Re: [matplotlib-devel] matplotlib 1.3.0rc4

[Paul H. <pmh...@gm...>]

Thanks, Christoph. Humming along just fine now.
-p


On Tue, Jul 2, 2013 at 11:10 AM, Christoph Gohlke <cg...@uc...> wrote:

> The official release candidate binaries include all the test data. The
> final binaries and the ones on my site do not because of the ~30 MB
> overhead.
>
>
> http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.3.0rc4/
>
> Christoph
>
>
> On 7/2/2013 11:04 AM, Paul Hobson wrote:
> > On Fri, Jun 21, 2013 at 10:42 AM, Michael Droettboom <md...@st...
> > <mailto:md...@st...>> wrote:
> >
> >     I have made a new release candidate (1.3.0rc4) that fixes the
> >     following vs. 1.3.0rc3:
> >
> >     - It doesn't add a setup.cfg file to the tarball
> >
> >     - It doesn't install the KnownFailure nose plugin as a pkg_resources
> >     entry_point (this conflicted with IPython's plugin of the same name)
> >
> >     - We get a known failure from the pep8 test if pep8 isn't installed
> >
> >     Hopefully that's enough to get to the point of giving this release
> >     candidate some wider exposure before putting out a final release. We
> >     can use some sprint time at Scipy to get this release polished if
> >     desired and necessary, too.
> >
> >     Mike
> >
> >
> > Hey folks,
> >
> > I just downloaded the RC4 Gohlke binary for 64-bit Python 3.3, and the
> > test suite is blowing up. Mostly related to the baseline images not
> > being included. Is there a trick to get the test suite to meaningfully
> > run on Windows? The test suite for Python 2.7.5 (via Anaconda) went
> > relevatively well(1 failure + 1 error, I think).
> >
> > Thanks,
> > -paul
> >
> >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> > http://p.sf.net/sfu/windows-dev2dev
> >
> >
> >
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Re: [matplotlib-devel] matplotlib 1.3.0rc4

[Christoph G. <cg...@uc...>]

The official release candidate binaries include all the test data. The 
final binaries and the ones on my site do not because of the ~30 MB 
overhead.

http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.3.0rc4/

Christoph


On 7/2/2013 11:04 AM, Paul Hobson wrote:
> On Fri, Jun 21, 2013 at 10:42 AM, Michael Droettboom <md...@st...
> <mailto:md...@st...>> wrote:
>
>     I have made a new release candidate (1.3.0rc4) that fixes the
>     following vs. 1.3.0rc3:
>
>     - It doesn't add a setup.cfg file to the tarball
>
>     - It doesn't install the KnownFailure nose plugin as a pkg_resources
>     entry_point (this conflicted with IPython's plugin of the same name)
>
>     - We get a known failure from the pep8 test if pep8 isn't installed
>
>     Hopefully that's enough to get to the point of giving this release
>     candidate some wider exposure before putting out a final release. We
>     can use some sprint time at Scipy to get this release polished if
>     desired and necessary, too.
>
>     Mike
>
>
> Hey folks,
>
> I just downloaded the RC4 Gohlke binary for 64-bit Python 3.3, and the
> test suite is blowing up. Mostly related to the baseline images not
> being included. Is there a trick to get the test suite to meaningfully
> run on Windows? The test suite for Python 2.7.5 (via Anaconda) went
> relevatively well(1 failure + 1 error, I think).
>
> Thanks,
> -paul
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Re: [matplotlib-devel] matplotlib 1.3.0rc4 (was: matplotlib 1.3.0rc3 tomorrow)

[Paul H. <pmh...@gm...>]

On Fri, Jun 21, 2013 at 10:42 AM, Michael Droettboom <md...@st...>wrote:

>  I have made a new release candidate (1.3.0rc4) that fixes the following
> vs. 1.3.0rc3:
>
> - It doesn't add a setup.cfg file to the tarball
>
> - It doesn't install the KnownFailure nose plugin as a pkg_resources
> entry_point (this conflicted with IPython's plugin of the same name)
>
> - We get a known failure from the pep8 test if pep8 isn't installed
>
> Hopefully that's enough to get to the point of giving this release
> candidate some wider exposure before putting out a final release.  We can
> use some sprint time at Scipy to get this release polished if desired and
> necessary, too.
>
> Mike
>

Hey folks,

I just downloaded the RC4 Gohlke binary for 64-bit Python 3.3, and the test
suite is blowing up. Mostly related to the baseline images not being
included. Is there a trick to get the test suite to meaningfully run on
Windows? The test suite for Python 2.7.5 (via Anaconda) went relevatively
well(1 failure + 1 error, I think).

Thanks,
-paul

[matplotlib-devel] matplotlib user survey 2013

[Michael D. <md...@st...>]

[Apologies for cross-posting]

The matplotlib developers want to hear from you!

We are conducting a user survey to determine how and where matplotlib is 
being used in order to focus its further development.

This should only take a couple of minutes.  To fill it out, visit:

https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ 
<https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ>

Please forward to your colleagues, particularly those who don't read 
these mailing lists.

Cheers,
Michael Droettboom, and the matplotlib team

[matplotlib-devel] In Memoriam, John D. Hunter III: 1968-2012

[Fernando P. <fpe...@gm...>]

Hi all,

after John's untimely passing we had a memorial service in Chicago,
but only a few on these lists were able to attend. At last week's
scipy conference I read a slightly edited version of the eulogy from
that memorial service, and I figured some of you might be interested
if you missed the conference:

http://blog.fperez.org/2013/07/in-memoriam-john-d-hunter-iii-1968-2012.html

Cheers,

f

--
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail

[matplotlib-devel] Reports from SciPy 2013

[Michael D. <md...@st...>]

SciPy 2013 was a great success.  I didn't get good headcount at the 
matplotlib BOF, but it was a good number, and we had 15 participants at 
various points during the sprints.  It was nice to see the diversity of 
experience with matplotlib at the sprints, and I hope we oldtimers were 
helpful to the newtimers getting started so they can continue to 
contribute in the future.  It was also great to put some faces to many 
of the talented names I've been seeing on github and the mailing list 
lately.

I've summarized the matplotlib BOF as well as the sprint.  I've also 
gone ahead and created MEP placeholders and issues for the major themes 
discussed.

https://github.com/matplotlib/matplotlib/wiki/Scipy-2013-BOF-Notes

https://github.com/matplotlib/matplotlib/wiki/Scipy-2013-sprinting-notes

Both of these documents are based on the realtime etherpad notes we made 
during the sessions, and on some of my own recollection, which is known 
to be incomplete or incorrect on occasion.  If I missed something, or 
you feel something isn't expressed in the right light, feel free to edit 
the wiki, but we should keep further discussion on the mailing list, 
github issues or other channels.  It would also be great to have 
volunteers to help write a MEP or two based on the BOF discussion.

Thanks again.  It was really nice to meet all of you!

Mike

Re: [matplotlib-devel] Reviving the matplotlib survey

[Thomas K. <th...@kl...>]

On 1 July 2013 16:09, Michael Droettboom <md...@st...> wrote:

> Everyone else: Are there any other changes you think we should make before
> we put this out?


We also started preparing a second user survey for IPython, but we haven't
yet launched it. I think our questions are broadly similar to yours, but if
you're interested, you can see our planned survey here:

https://docs.google.com/spreadsheet/viewform?formkey=dHF2WmlKdTZTRlZVRGFGTDgtUXFBVUE6MQ#gid=0

Thomas

Re: [matplotlib-devel] Reviving the matplotlib survey

[Benjamin R. <ben...@ou...>]

I would suggest clarifying the "how do you use matplotlib" question, or
perhaps refocusing it.

Cheers!
Ben Root


On Mon, Jul 1, 2013 at 11:09 AM, Michael Droettboom <md...@st...> wrote:

>  Last year, Paul wrote a survey for matplotlib so we could collect data on
> which versions of dependencies are being used, as well as to collect other
> data.
>
> You can see it here: survey<https://docs.google.com/spreadsheet/viewform?formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ>
>
> We dropped the ball on actually advertising this survey and getting some
> results, but I agree that we should do this.  Looking at it now, it's a
> little out of date in places (version of Python available, we should add
> Anaconda as options, etc.), but fundamentally I still think is very good.
>
> Paul: Can you give me edit permissions so I can update it?
>
> Everyone else: Are there any other changes you think we should make before
> we put this out?
>
> I think this, given enough responses, could be very helpful in determining
> our dependencies going forward, in addition to what I'm proposing in issue
> https://github.com/matplotlib/matplotlib/issues/2191.
>
> Cheers,
> Mike
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

[matplotlib-devel] Reviving the matplotlib survey

[Michael D. <md...@st...>]

Last year, Paul wrote a survey for matplotlib so we could collect data 
on which versions of dependencies are being used, as well as to collect 
other data.

You can see it here:survey 
<https://docs.google.com/spreadsheet/viewform?formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ>

We dropped the ball on actually advertising this survey and getting some 
results, but I agree that we should do this.  Looking at it now, it's a 
little out of date in places (version of Python available, we should add 
Anaconda as options, etc.), but fundamentally I still think is very good.

Paul: Can you give me edit permissions so I can update it?

Everyone else: Are there any other changes you think we should make 
before we put this out?

I think this, given enough responses, could be very helpful in 
determining our dependencies going forward, in addition to what I'm 
proposing in issue https://github.com/matplotlib/matplotlib/issues/2191.

Cheers,
Mike

Re: [matplotlib-devel] Error building documentation for 1.3.0rc4

[Michael D. <md...@st...>]

I've created https://github.com/matplotlib/matplotlib/issues/2187 for this.

On 07/01/2013 07:43 AM, Sandro Tosi wrote:
> On Mon, Jul 1, 2013 at 1:40 PM, Benjamin Root <ben...@ou...> wrote:
>> Make sure you do a make.py first and a git clean -fxd. I get these errors
>> whenever a file is moved around.
> I'm building from 1.3.0rc4 tarball, so no git on the way and make.py
> exists, else it would have failed calling it, not accessing a
> mpl_examples sub-file; the doc/mpl_examples path doesn't exists (dunno
> if it has to be a symlinks or what).
>
> Cheers,
> --
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] Error building documentation for 1.3.0rc4

[Sandro T. <san...@gm...>]

On Mon, Jul 1, 2013 at 1:40 PM, Benjamin Root <ben...@ou...> wrote:
> Make sure you do a make.py first and a git clean -fxd. I get these errors
> whenever a file is moved around.

I'm building from 1.3.0rc4 tarball, so no git on the way and make.py
exists, else it would have failed calling it, not accessing a
mpl_examples sub-file; the doc/mpl_examples path doesn't exists (dunno
if it has to be a symlinks or what).

Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Re: [matplotlib-devel] Error building documentation for 1.3.0rc4

[Benjamin R. <ben...@ou...>]

Make sure you do a make.py first and a git clean -fxd. I get these errors
whenever a file is moved around.

Ben Root
On Jun 30, 2013 6:09 PM, "Sandro Tosi" <san...@gm...> wrote:

> Hello,
> I'm preparing the Debian package for matplotlib 1.3.0rc4 but I got a
> failure while building documentation, here's the extract from the
> build log:
>
> ...
> # build the doc
> ( cd doc ; MPLCONFIGDIR=. MATPLOTLIBDATA=../lib/matplotlib/mpl-data/ \
> PYTHONPATH=../build/lib.linux-x86_64-2.7 ./make.py --small all )
> Running Sphinx v1.1.3
> Initializing GitHub plugin
> loading pickled environment... not yet created
> [autosummary] generating autosummary for: api/afm_api.rst,
> api/animation_api.rst, api/api_changes.rst, api/artist_api.rst,
> api/axes_api.rst, api/axis_api.rst, api/backend_bases_api.rst,
> api/backend_gtkagg_api.rst, api/backend_pdf_api.rst,
> api/backend_qt4agg_api.rst, ..., users/pyplot_tutorial.rst,
> users/recipes.rst, users/screenshots.rst, users/shell.rst,
> users/text_intro.rst, users/text_props.rst,
> users/tight_layout_guide.rst, users/transforms_tutorial.rst,
> users/usetex.rst, users/whats_new.rst
>
> building [html]: targets for 111 source files that are out of date
> updating environment: 112 added, 0 changed, 0 removed
> reading sources... [  0%] api/afm_api
> reading sources... [  1%] api/animation_api
> reading sources... [  2%] api/api_changes
> reading sources... [  3%] api/artist_api
> /usr/lib/python2.7/dist-packages/numpydoc/docscrape.py:117:
> UserWarning: Unknown section Accepts:
>   warn("Unknown section %s" % key)
>
> Exception occurred:
>   File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/states.py",
> line 195, in run
>     results = StateMachineWS.run(self, input_lines, input_offset)
>   File "/usr/lib/pymodules/python2.7/docutils/statemachine.py", line 237,
> in run
>     context, state, transitions)
>   File "/usr/lib/pymodules/python2.7/docutils/statemachine.py", line
> 458, in check_line
>     return method(match, context, next_state)
>   File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/states.py",
> line 2283, in explicit_markup
>     nodelist, blank_finish = self.explicit_construct(match)
>   File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/states.py",
> line 2295, in explicit_construct
>     return method(self, expmatch)
>   File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/states.py",
> line 2036, in directive
>     directive_class, match, type_name, option_presets)
>   File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/states.py",
> line 2087, in run_directive
>     result = directive_instance.run()
>   File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/__init__.py",
> line 382, in run
>     self.state, self.state_machine)
>   File
> "/home/morph/deb/build-area/matplotlib-1.3.0~rc4/build/lib.linux-x86_64-2.7/matplotlib/sphinxext/plot_directive.py",
> line 228, in plot_directive
>     return run(arguments, content, options, state_machine, state, lineno)
>   File
> "/home/morph/deb/build-area/matplotlib-1.3.0~rc4/build/lib.linux-x86_64-2.7/matplotlib/sphinxext/plot_directive.py",
> line 670, in run
>     with open(source_file_name, 'r') as fd:
> IOError: [Errno 2] No such file or directory:
>
> u'/home/morph/deb/build-area/matplotlib-1.3.0~rc4/doc/mpl_examples/pylab_examples/fancyarrow_demo.py'
> The full traceback has been saved in /tmp/sphinx-err-BQFK5w.log, if
> you want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> Either send bugs to the mailing list at
> <http://groups.google.com/group/sphinx-dev/>,
> or report them in the tracker at
> <http://bitbucket.org/birkenfeld/sphinx/issues/>. Thanks!
> Building HTML failed.
> ..
>
> and attached is the mentioned file.
>
> Please let me know if you want me to test something to have that fixed.
>
> Regards,
> --
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

[matplotlib-devel] Error building documentation for 1.3.0rc4

[Sandro T. <san...@gm...>]

Hello,
I'm preparing the Debian package for matplotlib 1.3.0rc4 but I got a
failure while building documentation, here's the extract from the
build log:

...
# build the doc
( cd doc ; MPLCONFIGDIR=. MATPLOTLIBDATA=../lib/matplotlib/mpl-data/ \
PYTHONPATH=../build/lib.linux-x86_64-2.7 ./make.py --small all )
Running Sphinx v1.1.3
Initializing GitHub plugin
loading pickled environment... not yet created
[autosummary] generating autosummary for: api/afm_api.rst,
api/animation_api.rst, api/api_changes.rst, api/artist_api.rst,
api/axes_api.rst, api/axis_api.rst, api/backend_bases_api.rst,
api/backend_gtkagg_api.rst, api/backend_pdf_api.rst,
api/backend_qt4agg_api.rst, ..., users/pyplot_tutorial.rst,
users/recipes.rst, users/screenshots.rst, users/shell.rst,
users/text_intro.rst, users/text_props.rst,
users/tight_layout_guide.rst, users/transforms_tutorial.rst,
users/usetex.rst, users/whats_new.rst

building [html]: targets for 111 source files that are out of date
updating environment: 112 added, 0 changed, 0 removed
reading sources... [  0%] api/afm_api
reading sources... [  1%] api/animation_api
reading sources... [  2%] api/api_changes
reading sources... [  3%] api/artist_api
/usr/lib/python2.7/dist-packages/numpydoc/docscrape.py:117:
UserWarning: Unknown section Accepts:
  warn("Unknown section %s" % key)

Exception occurred:
  File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/states.py",
line 195, in run
    results = StateMachineWS.run(self, input_lines, input_offset)
  File "/usr/lib/pymodules/python2.7/docutils/statemachine.py", line 237, in run
    context, state, transitions)
  File "/usr/lib/pymodules/python2.7/docutils/statemachine.py", line
458, in check_line
    return method(match, context, next_state)
  File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/states.py",
line 2283, in explicit_markup
    nodelist, blank_finish = self.explicit_construct(match)
  File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/states.py",
line 2295, in explicit_construct
    return method(self, expmatch)
  File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/states.py",
line 2036, in directive
    directive_class, match, type_name, option_presets)
  File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/states.py",
line 2087, in run_directive
    result = directive_instance.run()
  File "/usr/lib/pymodules/python2.7/docutils/parsers/rst/__init__.py",
line 382, in run
    self.state, self.state_machine)
  File "/home/morph/deb/build-area/matplotlib-1.3.0~rc4/build/lib.linux-x86_64-2.7/matplotlib/sphinxext/plot_directive.py",
line 228, in plot_directive
    return run(arguments, content, options, state_machine, state, lineno)
  File "/home/morph/deb/build-area/matplotlib-1.3.0~rc4/build/lib.linux-x86_64-2.7/matplotlib/sphinxext/plot_directive.py",
line 670, in run
    with open(source_file_name, 'r') as fd:
IOError: [Errno 2] No such file or directory:
u'/home/morph/deb/build-area/matplotlib-1.3.0~rc4/doc/mpl_examples/pylab_examples/fancyarrow_demo.py'
The full traceback has been saved in /tmp/sphinx-err-BQFK5w.log, if
you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error
message can be provided next time.
Either send bugs to the mailing list at
<http://groups.google.com/group/sphinx-dev/>,
or report them in the tracker at
<http://bitbucket.org/birkenfeld/sphinx/issues/>. Thanks!
Building HTML failed.
..

and attached is the mentioned file.

Please let me know if you want me to test something to have that fixed.

Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Re: [matplotlib-devel] Refactoring the axes module

[Damon M. <dam...@gm...>]

On Sat, Jun 29, 2013 at 2:18 PM, Nathaniel Smith <nj...@po...> wrote:

> pip *will* nuke old
> versions for you, and thus gives you a better chance of importing the
> code that was actually shipped.
>

Thanks Nathaniel, I didn't realise pip could snarf a local checkout.
 That's good to know.


-- 
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