On 07/17/2013 04:57 PM, Eric Firing wrote:
On 2013/07/17 3:14 AM, Michael Droettboom wrote:
Yes. This is great work!
Just to chime in (after having been away for most of this conversation) --
I think we can do this reorganization now without introducing any
implicit (or otherwise) use of
On 18 July 2013 15:27, Michael Droettboom md...@stsci.edu wrote:
On 07/17/2013 04:57 PM, Eric Firing wrote:
On 2013/07/17 3:14 AM, Michael Droettboom wrote:
Yes. This is great work!
Just to chime in (after having been away for most of this conversation)
--
I think we can do this
Yes. This is great work!
Just to chime in (after having been away for most of this conversation) --
I think we can do this reorganization now without introducing any
implicit (or otherwise) use of gca()/pyplot stuff in the Axes class
methods. Refactoring how the pyplot wrapper is done can
On 2013/07/17 3:14 AM, Michael Droettboom wrote:
Yes. This is great work!
Just to chime in (after having been away for most of this conversation) --
I think we can do this reorganization now without introducing any
implicit (or otherwise) use of gca()/pyplot stuff in the Axes class
Eric Firing efiring@... writes:
Anton,
Yes, I have done things like that in my own code, and basemap has a
similar ability to call gca() when an Axes is not supplied. One can
even perform the pyplot import on an as-needed basis instead of raising
an error. Nevetheless, it still
FYI, I have started the refactoring we discussed at scipy. I think
what tony is suggesting is the same thing.
I've created a work in progress pull request:
https://github.com/matplotlib/matplotlib/pull/2213
In the refactoring we discussed at Scipy, we did not mention the
pyplots wrapper at all.
Nelle, this is great! Thanks for getting the ball rolling!
Cheers,
-Tony
On Thu, Jul 11, 2013 at 6:31 AM, Nelle Varoquaux
nelle.varoqu...@gmail.comwrote:
FYI, I have started the refactoring we discussed at scipy. I think
what tony is suggesting is the same thing.
I've created a work in
Eric Firing efiring@... writes:
This would require pyplot to be imported by everything, wouldn't it?
That would completely defeat the strategy of having an OO level that
doesn't know about pyplot at all, and then having pyplot be the thin top
layer.
Requiring pyplot isn't necessary,
On 2013/07/10 1:11 AM, Anton Akhmerov wrote:
Eric Firing efiring@... writes:
This would require pyplot to be imported by everything, wouldn't it?
That would completely defeat the strategy of having an OO level that
doesn't know about pyplot at all, and then having pyplot be the thin top
On 2013/07/08 7:19 PM, Tony Yu wrote:
This is an idea that's been kicking around in my head for awhile.
Basically, the Axes class is way too expansive. Nelle made a major step
in the right direction with a PR that split it up into plotting and
non-plotting methods:
I second Eric's concern about pyplot being imported into everything. It
will really mess up the people that are embedding matplotlib into guis
because pyplot starts up gui mainloops if you are using an interactive
backend.
There is a genre of question on SO that is 'why isn't pyplot playing nice
On Tue, Jul 9, 2013 at 1:43 AM, Nelle Varoquaux
nelle.varoqu...@gmail.comwrote:
On 9 July 2013 08:24, Eric Firing efir...@hawaii.edu wrote:
On 2013/07/08 7:19 PM, Tony Yu wrote:
This is an idea that's been kicking around in my head for awhile.
Basically, the Axes class is way too
12 matches
Mail list logo
