matplotlib-devel — matplotlib developers

[matplotlib-devel] big memory leak when running tests?

[Eric F. <ef...@ha...>]

When I try to run matplotlib/tests.py on master, linux, python 2.7, in a 
virtual machine with 4GB, the memory use grows out of control.  Just 
running the test_axes chews up 1.5 G.  Has anyone else seen this?

Eric

[matplotlib-devel] MEP22 request for coments

[Federico A. <ari...@gm...>]

Hello

I didn't get any coments, positive or negative about the MEP22 implementation.

Please take a look at https://github.com/matplotlib/matplotlib/pull/2759

Thanks
Federico

-- 
Y yo que culpa tengo de que ellas se crean todo lo que yo les digo?

-- Antonio Alducin --

Re: [matplotlib-devel] when $HOME filesystem not writable

[<e.b...@ep...>]

Tom,

  I can use the current master branch. But in contrast to the issue on 
Google App Engine, the computer I am working on can see the HOME-dir, so 
it will set it. But then it has no read/write permissions on it (when 
running as a batch job).

Thanks,
Elena

  On Fri, 18 Apr 
2014, Thomas Caswell wrote:

> Elena,
>
> Is it possible for you to use the current master branch?  We
> definitely fixed this so that it would work with gae.
>
> Tom
>
> On Fri, Apr 18, 2014 at 9:32 AM,  <e.b...@ep...> wrote:
>> Hi,
>>
>>   I use matplotlib version 1.3.1.
>>
>> Elena
>>
>> On Fri, 18 Apr 2014, Benjamin Root wrote:
>>
>>> Which version of matplotlib are you using? I am fairly certain we fixed
>>> this problem for Google App Engine, which also does not have writable home
>>> directories.
>>>
>>> Ben Root
>>>
>>>
>>> On Fri, Apr 4, 2014 at 4:50 AM, <e.b...@ep...> wrote:
>>>
>>>> Hello,
>>>>
>>>>   I run my code from a batch system, from where the $HOME-filesystem is not
>>>> writable. In __init__.py in _get_home it finds ("~"), but then crashes
>>>> because it doesn't have access to it. I tried to set XDG_CONFIG_HOME and
>>>> MPLCONFIGDIR to circumvent this problem. But it still aborts. The only
>>>> solution I have found so far is to hack the code and replace ("~") by my
>>>> writable work-directory.
>>>>
>>>>   Is there any other way to tell it which directory to use - without having
>>>> to touch the actual code?
>>>>
>>>> Thanks,
>>>>          Elena
>>>>
>>>>
>>>> _____________________________________________________________________________
>>>>
>>>> Dr Elena Breitmoser
>>>> |EPCC|
>>>> The University of Edinburgh,
>>>> JCMB, Mayfield Rd,
>>>> UK-Edinburgh EH9 3JZ
>>>> Tel/Fax: +44 (0)131 650 6494/6555                              * Room
>>>> 3401*
>>>>
>>>> _____________________________________________________________________________
>>>>
>>>> "The University of Edinburgh is a charitable body, registered in
>>>>   Scotland, with registration number SC005336."
>>>>
>>>> --
>>>> The University of Edinburgh is a charitable body, registered in
>>>> Scotland, with registration number SC005336.
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>> "Graph Databases" is the definitive new guide to graph databases and their
>>>> applications. Written by three acclaimed leaders in the field,
>>>> this first edition is now available. Download your free book today!
>>>> http://p.sf.net/sfu/NeoTech
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Mat...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>>
>>>
>>
>>
>> Cheers,
>>          Elena
>>
>> _____________________________________________________________________________
>>
>> Dr Elena Breitmoser
>> |EPCC|
>> The University of Edinburgh,
>> JCMB, Mayfield Rd,
>> UK-Edinburgh EH9 3JZ
>> Tel/Fax: +44 (0)131 650 6494/6555                              * Room 3401*
>> _____________________________________________________________________________
>>
>> "The University of Edinburgh is a charitable body, registered in
>>   Scotland, with registration number SC005336."
>>
>> --
>> The University of Edinburgh is a charitable body, registered in
>> Scotland, with registration number SC005336.
>>
>>
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/NeoTech
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
> -- 
> Thomas Caswell
> tca...@gm...
>
>


Cheers,
         Elena

_____________________________________________________________________________

Dr Elena Breitmoser
|EPCC|
The University of Edinburgh,
JCMB, Mayfield Rd,
UK-Edinburgh EH9 3JZ
Tel/Fax: +44 (0)131 650 6494/6555                              * Room 3401*
_____________________________________________________________________________

"The University of Edinburgh is a charitable body, registered in
  Scotland, with registration number SC005336."

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Re: [matplotlib-devel] [IPython-dev] Interactive matplotlib figures in the IPython notebook

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

Hi Phil,

On Thu, Apr 24, 2014 at 6:57 AM, Phil Elson <pel...@gm...> wrote:

> Cross posted to IPython-dev and mpl-dev.
>
> Over the Easter holidays I had a chance to take a look at implementing a
> new matplotlib backend which would allow interactive figures inline in the
> IPython notebook. It's something that has been on the radar for a couple of
> years now, with work needed from both projects to make the functionality
> possible, so I'm pleased to have been able to submit a PR (
> https://github.com/matplotlib/matplotlib/pull/3008) to matplotlib which
> finally adds the nbagg backend - the final piece of the jigsaw.
>


this is great news, thanks for posting this! Most/all of us will be at
SciPy and staying for the sprints, so if there's remaining design work that
this uncovers that's needed for future improvements, please make note of it
and we can discuss it face to face.

Cheers

f

[matplotlib-devel] MEP22 update

[Federico A. <ari...@gm...>]

Hello everybody.

I just did a little update of the PR
https://github.com/matplotlib/matplotlib/pull/2759
This is the implementation of the MEP22.

I would like to have some feedback on this.
It is working and rebased so should merge cleanly.

There is an example in examples/user_interfaces/navigation.py that shows
the basic functionality of tools and toolbar reconfiguration and management.

Any comment is welcomed.

Thanks
Federico

[matplotlib-devel] Interactive matplotlib figures in the IPython notebook

[Phil E. <pel...@gm...>]

Cross posted to IPython-dev and mpl-dev.

Over the Easter holidays I had a chance to take a look at implementing a
new matplotlib backend which would allow interactive figures inline in the
IPython notebook. It's something that has been on the radar for a couple of
years now, with work needed from both projects to make the functionality
possible, so I'm pleased to have been able to submit a PR (
https://github.com/matplotlib/matplotlib/pull/3008) to matplotlib which
finally adds the nbagg backend - the final piece of the jigsaw.

It still needs a lot of polish, both at its core and superficially, but I
think it is at a stage which gives me confidence that the IPython Comm <->
mpl WebAgg approach is going to work to a reasonable degree, and is now at
a stage where it is readily usable by anybody running IPython >=2.0.

I really just wanted to draw your attention to the PR (early testers
welcome), and say thanks to everybody who has been involved in getting to
this stage, particularly Michael Droettboom, Jason Grout and everyone
involved in the IPython Comm interface.

Cheers,

Phil

Re: [matplotlib-devel] Automatic builds without NDEBUG?

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

On 04/19/2014 10:53 AM, Jouni K. Seppänen wrote:
> I was prompted by
>
> https://github.com/matplotlib/matplotlib/issues/2916
>
> to run some static checkers on the C/C++ extension modules, and I was
> going to submit some simple fixes as pull requests, including assertions
> of some preconditions. I just realized that our build system sets the
> -DNDEBUG compiler flag, which makes sense for release builds but could
> hide problems in test builds.
>
> Do any of our Travis, Launchpad, or other daily builds undefine NDEBUG?
>

I think this is brought in from the parameters that were used to build 
Python itself.  (The matplotlib build system doesn't explicitly add 
it).  If you build matplotlib with a debug Python, you get a debug 
matplotlib, however.  We could probably use a debug Python on Travis (in 
addition to the ones we already have) -- just a matter of installing the 
python-debug package and using the python-debug executable.

Mike

-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute

http://www.droettboom.com

Re: [matplotlib-devel] Automatic builds without NDEBUG?

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

On 19 April 2014 07:53, Jouni K. Seppänen <jk...@ik...> wrote:

> Do any of our Travis, Launchpad, or other daily builds undefine NDEBUG?


I don't think the Launchpad builds undefine that, unless Launchpad does it
for all builds by default.

Thomas

[matplotlib-devel] Automatic builds without NDEBUG?

[Jouni K. S. <jk...@ik...>]

I was prompted by

https://github.com/matplotlib/matplotlib/issues/2916

to run some static checkers on the C/C++ extension modules, and I was
going to submit some simple fixes as pull requests, including assertions
of some preconditions. I just realized that our build system sets the
-DNDEBUG compiler flag, which makes sense for release builds but could
hide problems in test builds.

Do any of our Travis, Launchpad, or other daily builds undefine NDEBUG?

-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Re: [matplotlib-devel] when $HOME filesystem not writable

[Thomas C. <tca...@gm...>]

Elena,

Is it possible for you to use the current master branch?  We
definitely fixed this so that it would work with gae.

Tom

On Fri, Apr 18, 2014 at 9:32 AM,  <e.b...@ep...> wrote:
> Hi,
>
>   I use matplotlib version 1.3.1.
>
> Elena
>
> On Fri, 18 Apr 2014, Benjamin Root wrote:
>
>> Which version of matplotlib are you using? I am fairly certain we fixed
>> this problem for Google App Engine, which also does not have writable home
>> directories.
>>
>> Ben Root
>>
>>
>> On Fri, Apr 4, 2014 at 4:50 AM, <e.b...@ep...> wrote:
>>
>>> Hello,
>>>
>>>   I run my code from a batch system, from where the $HOME-filesystem is not
>>> writable. In __init__.py in _get_home it finds ("~"), but then crashes
>>> because it doesn't have access to it. I tried to set XDG_CONFIG_HOME and
>>> MPLCONFIGDIR to circumvent this problem. But it still aborts. The only
>>> solution I have found so far is to hack the code and replace ("~") by my
>>> writable work-directory.
>>>
>>>   Is there any other way to tell it which directory to use - without having
>>> to touch the actual code?
>>>
>>> Thanks,
>>>          Elena
>>>
>>>
>>> _____________________________________________________________________________
>>>
>>> Dr Elena Breitmoser
>>> |EPCC|
>>> The University of Edinburgh,
>>> JCMB, Mayfield Rd,
>>> UK-Edinburgh EH9 3JZ
>>> Tel/Fax: +44 (0)131 650 6494/6555                              * Room
>>> 3401*
>>>
>>> _____________________________________________________________________________
>>>
>>> "The University of Edinburgh is a charitable body, registered in
>>>   Scotland, with registration number SC005336."
>>>
>>> --
>>> The University of Edinburgh is a charitable body, registered in
>>> Scotland, with registration number SC005336.
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Learn Graph Databases - Download FREE O'Reilly Book
>>> "Graph Databases" is the definitive new guide to graph databases and their
>>> applications. Written by three acclaimed leaders in the field,
>>> this first edition is now available. Download your free book today!
>>> http://p.sf.net/sfu/NeoTech
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>
>
>
> Cheers,
>          Elena
>
> _____________________________________________________________________________
>
> Dr Elena Breitmoser
> |EPCC|
> The University of Edinburgh,
> JCMB, Mayfield Rd,
> UK-Edinburgh EH9 3JZ
> Tel/Fax: +44 (0)131 650 6494/6555                              * Room 3401*
> _____________________________________________________________________________
>
> "The University of Edinburgh is a charitable body, registered in
>   Scotland, with registration number SC005336."
>
> --
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel



-- 
Thomas Caswell
tca...@gm...

Re: [matplotlib-devel] Code Review Request

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

A great quote from a GitHub presentation at SciPy 2012: "We consider Pull
Requests to be the *start* of a conversation".  Go ahead and make the pull
request. We can then review it, and you can make revisions to your branch
(the PR gets updated automatically as you push revisions up to it).

Cheers!
Ben Root


On Fri, Apr 18, 2014 at 11:11 AM, Benjamin Reedlunn <bre...@gm...>wrote:

> tcaswell suggested (https://github.com/matplotlib/matplotlib/issues/2972)
> I put together this example when I realized the difference between
> interpolation = 'none' and interpolation = 'nearest' in imshow().  The
> docstring for imshow() mentions this difference, but pictures are worth a
> thousand words.
>
> Here is the summary of my changes:
>
> https://github.com/Stretch97/matplotlib/compare/master...image-interpolation-example
>
> This is my first contribution to matplotlib.  I presume I wait until
> someone reviews my changes, and, if everything is ok, I submit a pull
> request.
>
> -Ben Reedlunn (Stretch97)
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

[matplotlib-devel] Code Review Request

[Benjamin R. <bre...@gm...>]

tcaswell suggested (https://github.com/matplotlib/matplotlib/issues/2972) I put together this example when I realized the difference between interpolation = 'none' and interpolation = 'nearest' in imshow().  The docstring for imshow() mentions this difference, but pictures are worth a thousand words.

Here is the summary of my changes:
https://github.com/Stretch97/matplotlib/compare/master...image-interpolation-example

This is my first contribution to matplotlib.  I presume I wait until someone reviews my changes, and, if everything is ok, I submit a pull request.

-Ben Reedlunn (Stretch97)

Re: [matplotlib-devel] when $HOME filesystem not writable

[<e.b...@ep...>]

Hi,

  I use matplotlib version 1.3.1.

Elena

On Fri, 18 Apr 2014, Benjamin Root wrote:

> Which version of matplotlib are you using? I am fairly certain we fixed
> this problem for Google App Engine, which also does not have writable home
> directories.
>
> Ben Root
>
>
> On Fri, Apr 4, 2014 at 4:50 AM, <e.b...@ep...> wrote:
>
>> Hello,
>>
>>   I run my code from a batch system, from where the $HOME-filesystem is not
>> writable. In __init__.py in _get_home it finds ("~"), but then crashes
>> because it doesn't have access to it. I tried to set XDG_CONFIG_HOME and
>> MPLCONFIGDIR to circumvent this problem. But it still aborts. The only
>> solution I have found so far is to hack the code and replace ("~") by my
>> writable work-directory.
>>
>>   Is there any other way to tell it which directory to use - without having
>> to touch the actual code?
>>
>> Thanks,
>>          Elena
>>
>>
>> _____________________________________________________________________________
>>
>> Dr Elena Breitmoser
>> |EPCC|
>> The University of Edinburgh,
>> JCMB, Mayfield Rd,
>> UK-Edinburgh EH9 3JZ
>> Tel/Fax: +44 (0)131 650 6494/6555                              * Room
>> 3401*
>>
>> _____________________________________________________________________________
>>
>> "The University of Edinburgh is a charitable body, registered in
>>   Scotland, with registration number SC005336."
>>
>> --
>> The University of Edinburgh is a charitable body, registered in
>> Scotland, with registration number SC005336.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/NeoTech
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>


Cheers,
         Elena

_____________________________________________________________________________

Dr Elena Breitmoser
|EPCC|
The University of Edinburgh,
JCMB, Mayfield Rd,
UK-Edinburgh EH9 3JZ
Tel/Fax: +44 (0)131 650 6494/6555                              * Room 3401*
_____________________________________________________________________________

"The University of Edinburgh is a charitable body, registered in
  Scotland, with registration number SC005336."

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Re: [matplotlib-devel] when $HOME filesystem not writable

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

Which version of matplotlib are you using? I am fairly certain we fixed
this problem for Google App Engine, which also does not have writable home
directories.

Ben Root


On Fri, Apr 4, 2014 at 4:50 AM, <e.b...@ep...> wrote:

> Hello,
>
>   I run my code from a batch system, from where the $HOME-filesystem is not
> writable. In __init__.py in _get_home it finds ("~"), but then crashes
> because it doesn't have access to it. I tried to set XDG_CONFIG_HOME and
> MPLCONFIGDIR to circumvent this problem. But it still aborts. The only
> solution I have found so far is to hack the code and replace ("~") by my
> writable work-directory.
>
>   Is there any other way to tell it which directory to use - without having
> to touch the actual code?
>
> Thanks,
>          Elena
>
>
> _____________________________________________________________________________
>
> Dr Elena Breitmoser
> |EPCC|
> The University of Edinburgh,
> JCMB, Mayfield Rd,
> UK-Edinburgh EH9 3JZ
> Tel/Fax: +44 (0)131 650 6494/6555                              * Room
> 3401*
>
> _____________________________________________________________________________
>
> "The University of Edinburgh is a charitable body, registered in
>   Scotland, with registration number SC005336."
>
> --
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

[matplotlib-devel] when $HOME filesystem not writable

[<e.b...@ep...>]

Hello,

  I run my code from a batch system, from where the $HOME-filesystem is not 
writable. In __init__.py in _get_home it finds ("~"), but then crashes 
because it doesn't have access to it. I tried to set XDG_CONFIG_HOME and 
MPLCONFIGDIR to circumvent this problem. But it still aborts. The only 
solution I have found so far is to hack the code and replace ("~") by my 
writable work-directory.

  Is there any other way to tell it which directory to use - without having 
to touch the actual code?

Thanks,
         Elena

_____________________________________________________________________________

Dr Elena Breitmoser
|EPCC|
The University of Edinburgh,
JCMB, Mayfield Rd,
UK-Edinburgh EH9 3JZ
Tel/Fax: +44 (0)131 650 6494/6555                              * Room 3401*
_____________________________________________________________________________

"The University of Edinburgh is a charitable body, registered in
  Scotland, with registration number SC005336."

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Re: [matplotlib-devel] mpl_toolkits tests module not included in install

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

Pinging on this issue now that we are about to include a new graph type in
mplot3d.

My thinking is that the determination of inclusion of this new
OptionalPackage should be made based on whether the regular tests package
was specified to be included *and* if the mpl_toolkits OptionalPackage was
specified to be included. Not exactly sure how that would get implemented,
but I am just getting my thoughts down on paper...

Cheers!
Ben Root



On Fri, Feb 28, 2014 at 10:34 AM, Benjamin Root <ben...@ou...> wrote:

> I was just about to put together a PR to whitelist the test_mplot3d.py so
> that Travis would do these tests by default, when I discovered that the
> test wasn't even available via the packaged install.
>
> In setupext.py, we have a mpl_toolkits OptionalPackage as well as a tests
> OptionalPackage, which are tests for mpl proper, and not mpl_toolkits.
> Should the tests for mpl_toolkits be considered a separate OptionalPackage
> with dependencies on mpl_toolkits and tests?
>
> I am already pushing the amount of free time I have to work on this,
> unfortunately.
>
> Cheers!
> Ben Root
>

[matplotlib-devel] EuroScipy Reminder: call for abstracts closes in 4 days

[Nelle V. <nel...@gm...>]

Hello everyone,

Just a quick reminder that the EuroScipy call for abstracts closes on the
14th: don't forget to submit your talk proposal! It is in four days only!

In short, EuroScipy is a cross-disciplinary gathering focused on the use
and development of the Python language in scientific research. This event
strives to bring together both users and developers of scientific tools, as
well as academic research and state of the art industry.

EuroSciPy 2014, the Seventh Annual Conference on Python in Science, takes
place in *Cambridge, UK on 27 - 30 August 2014*. The conference features
two days of tutorials followed by two days of scientific talks. The day
after the main conference, developer sprints will be organized on projects
of interest to attendees.

The topics presented at EuroSciPy are very diverse, with a focus on
advanced software engineering and original uses of Python and its
scientific libraries, either in theoretical or experimental research, from
both academia and the industry. The program includes keynotes, contributed
talks and posters.

Submissions for talks and posters are welcome on our website (
http://www.euroscipy.org/2014/). In your abstract, please provide details
on what Python tools are being employed, and how. The deadline for
submission is 14 April 2014.

Also until 14 April 2014, you can apply for a sprint session on 31 August
2014. See https://www.euroscipy.org/2014/calls/sprints/ for details.

Thanks,

N

[matplotlib-devel] Binary wheels for OSX

[Matthew B. <mat...@gm...>]

Hi,

I've just uploaded binary wheels for OSX to pypi.

If you're on Python.org python, then this should work

pip install --upgrade pip # if you're not on latest pip already
pip install matplotlib

I mean - you should get the binary wheel for matplotlib.

If fact this wheel will also work for Mac system python or homebrew or
macports if suitably renamed, but I put this current one up now, for
testing.

Please do let me know if you have any problems.

(By the way - this should also work in a fresh install / virtualenv,
because numpy is already pip'ed up with wheels).

Cheers,

Matthew

Re: [matplotlib-devel] PEP 8 change in Travis

[Thomas C. <tca...@gm...>]

My PR to squelch the seemingly new tests passes travis.  Unless
someone strongly protests, I will merge it later this afternoon so we
can get back to our normally scheduled testing.

If we want to discuss turning some of the tests back on we can have
that discussion later.

Tom

On Thu, Mar 27, 2014 at 11:40 AM, Phil Elson <phi...@gm...> wrote:
> I see your point Paul, but from my perspective matplotlib's codebase is
> slowly but surely being tidied up, and the consistently styled code is
> making it easier to read, maintain and enhance.
>
> Re-quoting Guido:
>
>
>     Let's try to make new stdlib modules use the best style we
>     can think of, but limit the time spent fretting over code
>     that's already there.
>
> We've also taken this view and as a result have whole sub-packages which we
> do not check the PEP8 tests against
> (https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/tests/test_coding_standards.py#L41).
> However, I must add that it is actually quite rewarding to go through ugly
> code and turn it into something approaching consistent [I encourage you to
> try it when the sun isn't shining in California ;) ], not not mention it
> being a great way to get involved in the development of mpl (actually in the
> beginning I think that is how Thomas and Nelle became frequent committers).
>
> So in summary I agree they are just *guidelines*, not strict rules, but we
> have to maintain a highly collaborative repository of code and we ultimately
> need to make it as readable and maintainable as possible - the best way of
> doing that IMHO is to automate the testing using tools such as pep8 so that
> when we review PRs we only need to focus on behaviour, and not on whether
> there are trailing whitespace characters etc.
>
>
>
>
>
>
>
>
> On 27 March 2014 01:51, Thomas Caswell <tca...@gm...> wrote:
>>
>> At any rate, I have a PR (#2930) that should make it pass cleanly again.
>>
>> On the bright side, it looks like one of the changes is 1.5 is that
>> long unbreakable lines will get ignored by E501 so urls are safe
>> again.
>>
>>
>>
>> On Wed, Mar 26, 2014 at 6:10 PM, Paul Ivanov <pi...@be...> wrote:
>> > Nelle Varoquaux, on 2014-03-26 21:27,  wrote:
>> >> > Does anyone know why we are seeing a huge number of PEP 8 failures
>> >> > now?
>> >> >   It looks to me like it is a change in which modules are subject to
>> >> > the
>> >> > test, or in which tests are grounds for failure.  I don't know how
>> >> > all
>> >> > this is set up, though.
>> >>
>> >> If it started very recently, it could be linked to the new release.
>> >> They
>> >> have started to make "none backward" compatible version, in the sense
>> >> that
>> >> the stylechecker is increasingly strict. It is very annoying...
>> >
>> > Can we not revisit (and possibly revert) the morally absolutist
>> > PEP-8 or death position that matplotlib has taken?
>> >
>> > Quoting GvR (emphasis mine):
>> >
>> >     All I want to say is, people lighten up. The style guide
>> >     can't solve all your problems. You are never going to have
>> >     all code compliant. Use the style guide when it helps, *ignore
>> >     it when it's in the way*
>> >
>> > And from that same email:
>> >
>> >     Let's try to make new stdlib modules use the best style we
>> >     can think of, but limit the time spent fretting over code
>> >     that's already there.
>> >
>> >
>> > The rest of the message is useful to read:
>> > https://mail.python.org/pipermail/python-dev/2010-November/105681.html
>> >
>> > Another reason for not being so rigid about  PEP-8 is that its a
>> > living document. Are we really doing massive search-and-replace
>> > changes to the codebase just to comply with a moving target?
>> >
>> > best,
>> > --
>> >                    _
>> >                   / \
>> >                 A*   \^   -
>> >              ,./   _.`\\ / \
>> >             / ,--.S    \/   \
>> >            /  `"~,_     \    \
>> >      __o           ?
>> >    _ \<,_         /:\
>> > --(_)/-(_)----.../ | \
>> > --------------.......J
>> > Paul Ivanov
>> > http://pirsquared.org
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > _______________________________________________
>> > Matplotlib-devel mailing list
>> > Mat...@li...
>> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>>
>> --
>> Thomas Caswell
>> tca...@gm...
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>



-- 
Thomas Caswell
tca...@gm...

Re: [matplotlib-devel] PEP 8 change in Travis

[Thomas C. <tca...@gm...>]

At any rate, I have a PR (#2930) that should make it pass cleanly again.

On the bright side, it looks like one of the changes is 1.5 is that
long unbreakable lines will get ignored by E501 so urls are safe
again.



On Wed, Mar 26, 2014 at 6:10 PM, Paul Ivanov <pi...@be...> wrote:
> Nelle Varoquaux, on 2014-03-26 21:27,  wrote:
>> > Does anyone know why we are seeing a huge number of PEP 8 failures now?
>> >   It looks to me like it is a change in which modules are subject to the
>> > test, or in which tests are grounds for failure.  I don't know how all
>> > this is set up, though.
>>
>> If it started very recently, it could be linked to the new release. They
>> have started to make "none backward" compatible version, in the sense that
>> the stylechecker is increasingly strict. It is very annoying...
>
> Can we not revisit (and possibly revert) the morally absolutist
> PEP-8 or death position that matplotlib has taken?
>
> Quoting GvR (emphasis mine):
>
>     All I want to say is, people lighten up. The style guide
>     can't solve all your problems. You are never going to have
>     all code compliant. Use the style guide when it helps, *ignore
>     it when it's in the way*
>
> And from that same email:
>
>     Let's try to make new stdlib modules use the best style we
>     can think of, but limit the time spent fretting over code
>     that's already there.
>
>
> The rest of the message is useful to read:
> https://mail.python.org/pipermail/python-dev/2010-November/105681.html
>
> Another reason for not being so rigid about  PEP-8 is that its a
> living document. Are we really doing massive search-and-replace
> changes to the codebase just to comply with a moving target?
>
> best,
> --
>                    _
>                   / \
>                 A*   \^   -
>              ,./   _.`\\ / \
>             / ,--.S    \/   \
>            /  `"~,_     \    \
>      __o           ?
>    _ \<,_         /:\
> --(_)/-(_)----.../ | \
> --------------.......J
> Paul Ivanov
> http://pirsquared.org
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel



-- 
Thomas Caswell
tca...@gm...

Re: [matplotlib-devel] PEP 8 change in Travis

[Paul I. <pi...@be...>]

Nelle Varoquaux, on 2014-03-26 21:27,  wrote:
> > Does anyone know why we are seeing a huge number of PEP 8 failures now?
> >   It looks to me like it is a change in which modules are subject to the
> > test, or in which tests are grounds for failure.  I don't know how all
> > this is set up, though.
> 
> If it started very recently, it could be linked to the new release. They
> have started to make "none backward" compatible version, in the sense that
> the stylechecker is increasingly strict. It is very annoying...

Can we not revisit (and possibly revert) the morally absolutist
PEP-8 or death position that matplotlib has taken?

Quoting GvR (emphasis mine):

    All I want to say is, people lighten up. The style guide
    can't solve all your problems. You are never going to have
    all code compliant. Use the style guide when it helps, *ignore
    it when it's in the way*

And from that same email:

    Let's try to make new stdlib modules use the best style we
    can think of, but limit the time spent fretting over code
    that's already there.
    

The rest of the message is useful to read:
https://mail.python.org/pipermail/python-dev/2010-November/105681.html

Another reason for not being so rigid about  PEP-8 is that its a
living document. Are we really doing massive search-and-replace
changes to the codebase just to comply with a moving target?

best,
-- 
                   _
                  / \
                A*   \^   -
             ,./   _.`\\ / \
            / ,--.S    \/   \
           /  `"~,_     \    \
     __o           ?
   _ \<,_         /:\
--(_)/-(_)----.../ | \
--------------.......J
Paul Ivanov
http://pirsquared.org

Re: [matplotlib-devel] PEP 8 change in Travis

[Nelle V. <nel...@gm...>]

> Does anyone know why we are seeing a huge number of PEP 8 failures now?
>   It looks to me like it is a change in which modules are subject to the
> test, or in which tests are grounds for failure.  I don't know how all
> this is set up, though.
>

If it started very recently, it could be linked to the new release. They
have started to make "none backward" compatible version, in the sense that
the stylechecker is increasingly strict. It is very annoying...


>
> Eric
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

[matplotlib-devel] PEP 8 change in Travis

[Eric F. <ef...@ha...>]

Does anyone know why we are seeing a huge number of PEP 8 failures now? 
  It looks to me like it is a change in which modules are subject to the 
test, or in which tests are grounds for failure.  I don't know how all 
this is set up, though.

Eric

[matplotlib-devel] OK to upload wheels to pypi?

[Matthew B. <mat...@gm...>]

Hi,

I've built and tested some binary wheels for OSX - available here:

https://nipy.bic.berkeley.edu/scipy_installers/

I'd really like to upload these to pypi so that people get them by
default with 'pip install matplotlb'.  Is that OK?  Can someone give
me permission to do that?

Thanks a lot,

Matthew

Re: [matplotlib-devel] I added a wheels build to binary build framework

[Matthew B. <mat...@gm...>]

Hi,

On Mon, Mar 24, 2014 at 6:29 AM, Benjamin Root <ben...@ou...> wrote:
> I thought we fixed this one...
>
> Seems like we haven't as there is an open issue for it:
> https://github.com/matplotlib/matplotlib/issues/2842

Sorry - I didn't say - but the wheels are for the 1.3.1 release...

Cheers,

Matthew