matplotlib-devel Mailing List for matplotlib

Sure, here it is:
https://github.com/matplotlib/matplotlib/pull/3096
On Fri, May 30, 2014 at 4:21 PM, Paul Hobson <pmh...@gm...> wrote:
> Peter,
>
> Can you submit this as a pull request on github?
> http://matplotlib.org/devel/gitwash/git_development.html
>
>
> On Fri, May 30, 2014 at 12:37 PM, Peter St. John <pet...@gm...>
> wrote:
>
>> Finally made this into a patch to allow the dynamic updating of the
>> axes.labelpad parameter.
>> Hope this is in the appropriate format!
>>
>> Thanks,
>> -- Peter
>>
>>
>> On Mon, Oct 28, 2013 at 10:45 AM, Peter St. John <pet...@gm...
>> > wrote:
>>
>>> Hi Matplotlib-users,
>>>
>>> I found it was useful to be able to change the default 'Axis.labelpad'
>>> parameter, since this value didn't scale when changing the default figure
>>> size (in my opinion its easier to prepare figures for publication assuming
>>> they'll need to fit in a 1-column figure). I don't consider myself
>>> experienced enough to attempt to contribute a patch, but nevertheless here
>>> is the hack I used in case anyone has a similar problem:
>>>
>>> axis.py, line 652:
>>> original: self.labelpad = 5
>>> changed : self.labelpad = rcParams['axes.labelpad']
>>>
>>> Then, in rcsetup.py, I added the line (at 578):
>>> 'axes.labelpad' : [5.0, validate_float],
>>>
>>> This lets you put
>>> axes.labelpad : 3
>>> for instance, in your matplotlibrc to change the default label padding.
>>>
>>> Anyways, not sure if this is the right mailing list for this type of
>>> thing, but just thought I'd contribute it nevertheless.
>>>
>>> Best,
>>> -- Peter
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Time is money. Stop wasting it! Get your web API in 5 minutes.
>> www.restlet.com/download
>> http://p.sf.net/sfu/restlet
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>

Peter,
Can you submit this as a pull request on github?
http://matplotlib.org/devel/gitwash/git_development.html
On Fri, May 30, 2014 at 12:37 PM, Peter St. John <pet...@gm...>
wrote:
> Finally made this into a patch to allow the dynamic updating of the
> axes.labelpad parameter.
> Hope this is in the appropriate format!
>
> Thanks,
> -- Peter
>
>
> On Mon, Oct 28, 2013 at 10:45 AM, Peter St. John <pet...@gm...>
> wrote:
>
>> Hi Matplotlib-users,
>>
>> I found it was useful to be able to change the default 'Axis.labelpad'
>> parameter, since this value didn't scale when changing the default figure
>> size (in my opinion its easier to prepare figures for publication assuming
>> they'll need to fit in a 1-column figure). I don't consider myself
>> experienced enough to attempt to contribute a patch, but nevertheless here
>> is the hack I used in case anyone has a similar problem:
>>
>> axis.py, line 652:
>> original: self.labelpad = 5
>> changed : self.labelpad = rcParams['axes.labelpad']
>>
>> Then, in rcsetup.py, I added the line (at 578):
>> 'axes.labelpad' : [5.0, validate_float],
>>
>> This lets you put
>> axes.labelpad : 3
>> for instance, in your matplotlibrc to change the default label padding.
>>
>> Anyways, not sure if this is the right mailing list for this type of
>> thing, but just thought I'd contribute it nevertheless.
>>
>> Best,
>> -- Peter
>>
>
>
>
> ------------------------------------------------------------------------------
> Time is money. Stop wasting it! Get your web API in 5 minutes.
> www.restlet.com/download
> http://p.sf.net/sfu/restlet
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Finally made this into a patch to allow the dynamic updating of the
axes.labelpad parameter.
Hope this is in the appropriate format!
Thanks,
-- Peter
On Mon, Oct 28, 2013 at 10:45 AM, Peter St. John <pet...@gm...>
wrote:
> Hi Matplotlib-users,
>
> I found it was useful to be able to change the default 'Axis.labelpad'
> parameter, since this value didn't scale when changing the default figure
> size (in my opinion its easier to prepare figures for publication assuming
> they'll need to fit in a 1-column figure). I don't consider myself
> experienced enough to attempt to contribute a patch, but nevertheless here
> is the hack I used in case anyone has a similar problem:
>
> axis.py, line 652:
> original: self.labelpad = 5
> changed : self.labelpad = rcParams['axes.labelpad']
>
> Then, in rcsetup.py, I added the line (at 578):
> 'axes.labelpad' : [5.0, validate_float],
>
> This lets you put
> axes.labelpad : 3
> for instance, in your matplotlibrc to change the default label padding.
>
> Anyways, not sure if this is the right mailing list for this type of
> thing, but just thought I'd contribute it nevertheless.
>
> Best,
> -- Peter
>

Hello all,
Sorry to be writing this at this late point, but I've been hoping I 
could find a way around it. I won't be able to attend an extra day at 
either end of Scipy year, both due to personal commitments and new 
funding constraints at NASA. I do plan to attend/host the matplotlib 
sprint again, however, which is not a bad opportunity to catch up on 
some of these issues.
So, an extra developer summit day is still possible if someone else is 
able to organize it -- I just, unfortunately, won't be able to attend. 
We can still use the matplotlib donated funds to cover the cost of the 
extra hotel night (assuming the numbers of people wanting to do that is 
not too large) and meeting space (if the cost is not too high, though 
maybe locals like Damon have a connection for free and/or cheap space). 
For reimbursement, I would need a receipt for that hotel night (ideally 
with that one night broken out individually), which will then be 
submitted to numfocus, who will reimburse you directly.
Sorry to be uncommunicative on this (and uncommunicative in general 
lately). I hope something can still work out at this late date!
Mike
On 02/27/2014 11:28 AM, Michael Droettboom wrote:
> How many matplotlib developers are planning to attend SciPy this year?
>
> If we used some of our funds to support an extra hotel night, would any
> of you be interested in spending an extra day for a "matplotlib
> developer summit" to discuss matplotlib projects? This would be in
> addition to the sprints, which I see probably being a larger group. Your
> response isn't a committment at this point, I'm just trying to gauge how
> much interest there might be.
>
> Mike
>
-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
http://www.droettboom.com

On Thu, May 22, 2014 at 12:10 PM, Nathan Goldbaum <nat...@gm...>
wrote:
>
> Any reason you're trying to compile with gcc? I think most of the
homebrew build recipes are tested using clang.
>
>
Thanks, that worked. (I had CC=gcc to keep things compatible with linux).
For anyone coming to this thread with the same error, note that you also
need to do
export CC=/usr/bin/clang
export FC-=/usr/local/bin/fortran
to get
pip install scipy
to work.

Any reason you're trying to compile with gcc? I think most of the homebrew
build recipes are tested using clang.
On Thu, May 22, 2014 at 12:07 PM, lecture notes <mkp...@gm...> wrote:
> I'm trying to get matplotlib working with the following setup on OSX 10.9.3
>
> rail:~ brew$ gcc --version
> gcc (GCC) 4.8.2
>
> rail:~ brew$ python --version
> Python 2.7.6
>
> pip install git+git://github.com/matplotlib/matplotlib.git (as of today
> at 11am PDT)
>
> Problem 1: couldn't find a freetype header -- googling supplied the fix:
>
> sudo ln -s /usr/X11/include/freetype2/freetype /usr/X11/include/.
>
> per
> http://stackoverflow.com/questions/19697457/numpy-matplotlib-install-error-ftheader-h-no-such-file-or-directory
>
> Problem 2: I'm getting a fatal syntax error in _macosx.m:
>
> /usr/local/bin/gcc -fno-strict-aliasing -fno-common -dynamic
> -I/usr/local/include -I/usr/local/opt/sqlite/include -DNDEBUG -g -fwrapv
> -O3 -Wall
> -DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_backends__macosx_ARRAY_API
> -DPYCXX_ISO_CPP_LIB=1
> -I/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/include
> -I/usr/local/include -I/usr/include -I/usr/X11/include -I.
> -Iextern/agg24/include -Iextern
> -I/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/include/python2.7
> -c src/_macosx.m -o build/temp.macosx-10.8-x86_64-2.7/src/_macosx.o
>
> In file included from /usr/include/Availability.h:148:0,
>
> from
> /usr/local/Cellar/gcc/4.8.2_1/lib/gcc/x86_64-apple-darwin13.2.0/4.8.2/include-fixed/math.h:46,
>
> from
> /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:19,
>
> from
> /System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6,
>
> from
> /System/Library/Frameworks/Cocoa.framework/Headers/Cocoa.h:12,
>
> from src/_macosx.m:1:
>
> /System/Library/Frameworks/Foundation.framework/Headers/NSUserNotification.h:16:45:
> error: expected ',' or '}' before '__attribute__'
>
> NSUserNotificationActivationTypeReplied NS_AVAILABLE(10_9, NA) = 3
>
>
> thanks in advance for suggestions on how to proceed -- Phil
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

I'm trying to get matplotlib working with the following setup on OSX 10.9.3
rail:~ brew$ gcc --version
gcc (GCC) 4.8.2
rail:~ brew$ python --version
Python 2.7.6
 pip install git+git://github.com/matplotlib/matplotlib.git (as of today at
11am PDT)
Problem 1: couldn't find a freetype header -- googling supplied the fix:
 sudo ln -s /usr/X11/include/freetype2/freetype /usr/X11/include/.
per
http://stackoverflow.com/questions/19697457/numpy-matplotlib-install-error-ftheader-h-no-such-file-or-directory
Problem 2: I'm getting a fatal syntax error in _macosx.m:
/usr/local/bin/gcc -fno-strict-aliasing -fno-common -dynamic
-I/usr/local/include -I/usr/local/opt/sqlite/include -DNDEBUG -g -fwrapv
-O3 -Wall
-DPY_ARRAY_UNIQUE_SYMBOL=MPL_matplotlib_backends__macosx_ARRAY_API
-DPYCXX_ISO_CPP_LIB=1
-I/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/include
-I/usr/local/include -I/usr/include -I/usr/X11/include -I.
-Iextern/agg24/include -Iextern
-I/usr/local/Cellar/python/2.7.6/Frameworks/Python.framework/Versions/2.7/include/python2.7
-c src/_macosx.m -o build/temp.macosx-10.8-x86_64-2.7/src/_macosx.o
In file included from /usr/include/Availability.h:148:0,
 from
/usr/local/Cellar/gcc/4.8.2_1/lib/gcc/x86_64-apple-darwin13.2.0/4.8.2/include-fixed/math.h:46,
 from
/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:19,
 from
/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6,
 from
/System/Library/Frameworks/Cocoa.framework/Headers/Cocoa.h:12,
 from src/_macosx.m:1:
/System/Library/Frameworks/Foundation.framework/Headers/NSUserNotification.h:16:45:
error: expected ',' or '}' before '__attribute__'
 NSUserNotificationActivationTypeReplied NS_AVAILABLE(10_9, NA) = 3
thanks in advance for suggestions on how to proceed -- Phil

The nascent 1.4.x code is working fine for me to fire up my
interactive graphs served by a Tornado server. I'm interested in
providing an interface via a web application server like Django
though. I've only begun to look at the webagg backend code, but if I
read the comments correctly at the top of the files, it would seem
that I need to create a backend_webdjango.py module which relies on
the backend_webagg_core module for the heavy lifting, and interfaces
with the Django environment. Is this about correct? Has anyone
implemented a proof-of-concept of matplotlib running inside any web
application server?
Thx,
Skip

On 05/16/2014 04:17 AM, Eric Firing wrote:
> On 2014年05月15日 5:16 PM, Thomas Caswell wrote:
>> Sorry for dropping the ball on moving things forward.
> On the contrary, you have been doing a great job on this, and you
> deserve a lot of thanks from all of us.
Yes -- I can't thank you enough. I've been feeling bad about getting 
being so overstretched on non-matplotlib things these past few months 
(in related news, STScI is hiring!) but I know it's in capable hands, 
even if I don't have time to dig in and help like I used to.
>
>> I would propose a feature freeze this weekend and the goal of getting
>> the first RC out by the end of the month. We should probably plan a
>> hangout sometime in between now and then if there is stuff we want to
>> work out at a lower latency.
> Feature freeze: good.
>
>> There are 62 open issues tagged as 1.4.0, but there are a number of
>> issues which have both an issue and a PR so it is more like ~40 open
>> issues. At least some of these will probably be punted.
> Agreed!
> It's a daunting list.
>
>> The major features that are outstanding and need work/discussion:
>> - grid lines in polar plots (#1441, #1730, #1847, #2203
>> - Qt5 (#2471) do we want to squeeze this in? ipython has it working
>> so I don't think it will be too bad (despite all the furry in that
>> issue).
>> - turning down the garbage collection calls (#3045)
>> - #2986 axes order for event handling
>>
>> Bugs this still need patches:
>> - auto-scale + sharex/sharey + aspect heuristics don't always work
>> (#1325, #2492). I could be convinced to punt this as it is 'fixed' by
>> just setting the limits by hand + the forcing parameters.
>> - #2856 / #2900 issues with saving animations
>> - #3065 font priority test failure
>> - #2698 deal with empty lines in text + box
>> + #3039 tornado should not be an install dependency
>> + #3042 revert changes to default style in boxplot
>> - #2941 / #3012 calling cla() in `set_ticks_position`
>> - #2945 issues with hist, patch in issue
>> - #2977 pyqt string validation (patch in issue)
>>
>> Bug PRs that need minor work:
>> - #1981 / #2662 mark-every upgrade
>> - #2150 / #2942 fixing issues with auto-limit + 0 height bar plots
>> - #2394 / #2951 issues in mpl_toolkits.axes_grid1.anchored_artists
>> - #2475 / #2843 contour labels (release critical)
>> - #3000 / #3017 multi-line in pgf
>>
>> Bug PRs that need major work:
>> - #1012, animation related PR from jdh.
>> - #2366 / #2738 errorbar + linestyle (this is one of mine, Eric does
>> not like it)
>> - #2828 / #2927 issue with mutable objects, ==, and hash
>>
>>
>> Documentation:
>> - #2350 annotation arrow example, code in issue needs PR
>> - #2742 how to do a re-base (mine, needs work)
>> - #2796 offset on default formatter documentation
>> - #2603 suggested edit in issue
>> - #2908 404 in docs
>> - #2918 re-write contribution guide lines to match reality
>> - #2929 doc about clip-on
>> - #2999 install documentation
>> - #3004 remove all references to nxutils
>> - #3035 documentation in Polygon object
>> - #3055 maybe add warning to get_window_extent
>>
>> PRs that need review:
>> - #2288 / #3053
>> - #2602 / #3015 fix stem plots
>> - #2822 (documentation clarification)
>> - #2952 / #2518 turn off clipping on all pie charts
>>
>> feature PRs that need minor work:
>> - #2855 adds flag to spy, pep8 issue
>> - #2541 / 2874 fixes mouse over text in polar mode (rebase)
>> - #2961 3D quiver
>> - #2996 violin plots
>>
>> No idea what to do with
>> - #2025, tkagg + osx framework build stuff
>>
>> Maybe resolved:
>> - issues with the screen not matching the saved images (#1441, #2935,
>> #2831, and #2889) might all be fixed by #3054
>>
>> I think I am going to start just doing merges with CHANGELOG conflicts
>> on my local computer and pushing to matplotlib/master as the amount of
>> re-bases we end up needing is getting absurd.
> Maybe this problem could be reduced by having a directory for CHANGELOG
> chunks, one file per PR, with the PR number as the filename. Then at
> release time they could be concatenated, edited, appended to the real
> CHANGELOG, and deleted.
>
> Another approach would be to have the CHANGELOG entry as an identifiable
> chunk in the commit message. Then they would be extracted and dealt
> with at release time, as above.
Another solution for CHANGELOG entries that we use in the astropy 
project is to have section headers in the CHANGELOG file upfront (put in 
at the beginning of each release cycle). Then merge conflicts tend to 
be localized to one subsystem and are less frequent. But that's only a 
partial solution. Eric's suggestions also make a lot of sense.
Mike
>
> Eric
>
>> Tom
>>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
http://www.droettboom.com

Thomas Kluyver, on 2014年05月16日 08:56, wrote:
> On 16 May 2014 01:17, "Eric Firing" <ef...@ha...> wrote:
> > Maybe this problem could be reduced by having a directory for CHANGELOG
> > chunks, one file per PR, with the PR number as the filename. Then at
> > release time they could be concatenated, edited, appended to the real
> > CHANGELOG, and deleted.
> 
> We already do this in ipython for our 'whatsnew' document. We allow
> arbitrary filenames rather than using PR numbers, and then we concatenate
> everything from the directory periodically. You're welcome to copy our
> script to do this.
Yes, this has been working out quite nicely for us, and we
started doing it for the very same reasons - to keep conflicts to
a minimum while making it easier to keep track of everything that
has gone in.
Here's the direct link to our script:
https://github.com/ipython/ipython/blob/master/tools/update_whatsnew.py
-- 
 _
 / \
 A* \^ -
 ,./ _.`\\ / \
 / ,--.S \/ \
 / `"~,_ \ \
 __o ?
 _ \<,_ /:\
--(_)/-(_)----.../ | \
--------------.......J
Paul Ivanov
http://pirsquared.org

On 16 May 2014 01:17, "Eric Firing" <ef...@ha...> wrote:
> Maybe this problem could be reduced by having a directory for CHANGELOG
> chunks, one file per PR, with the PR number as the filename. Then at
> release time they could be concatenated, edited, appended to the real
> CHANGELOG, and deleted.
We already do this in ipython for our 'whatsnew' document. We allow
arbitrary filenames rather than using PR numbers, and then we concatenate
everything from the directory periodically. You're welcome to copy our
script to do this.
Thomas

Thanks for doing all this work, 1.4 is more than overdue!
I justed wanted to chime in on Qt 5: Put it in and mark
the support as experimental. So we can fix it in minor
releases, also without exposure bugs won't be found.
Till

On Fri, May 16, 2014 at 4:17 AM, Eric Firing <ef...@ha...> wrote:
> Maybe this problem could be reduced by having a directory for CHANGELOG
> chunks, one file per PR, with the PR number as the filename. Then at
> release time they could be concatenated, edited, appended to the real
> CHANGELOG, and deleted.
I like this idea a lot. PR number as name is a little awkward as you
don't know the PR# till you submit the PR. As long as they all go in
the same folder and we use a quasi-unique scheme
(YYYY-MM-DD-[initials]_[n].txt) to name them it should be fine
-- 
Thomas Caswell
tca...@gm...

On 2014年05月15日 5:16 PM, Thomas Caswell wrote:
> Sorry for dropping the ball on moving things forward.
On the contrary, you have been doing a great job on this, and you 
deserve a lot of thanks from all of us.
>
> I would propose a feature freeze this weekend and the goal of getting
> the first RC out by the end of the month. We should probably plan a
> hangout sometime in between now and then if there is stuff we want to
> work out at a lower latency.
Feature freeze: good.
>
> There are 62 open issues tagged as 1.4.0, but there are a number of
> issues which have both an issue and a PR so it is more like ~40 open
> issues. At least some of these will probably be punted.
Agreed!
It's a daunting list.
>
> The major features that are outstanding and need work/discussion:
> - grid lines in polar plots (#1441, #1730, #1847, #2203
> - Qt5 (#2471) do we want to squeeze this in? ipython has it working
> so I don't think it will be too bad (despite all the furry in that
> issue).
> - turning down the garbage collection calls (#3045)
> - #2986 axes order for event handling
>
> Bugs this still need patches:
> - auto-scale + sharex/sharey + aspect heuristics don't always work
> (#1325, #2492). I could be convinced to punt this as it is 'fixed' by
> just setting the limits by hand + the forcing parameters.
> - #2856 / #2900 issues with saving animations
> - #3065 font priority test failure
> - #2698 deal with empty lines in text + box
> + #3039 tornado should not be an install dependency
> + #3042 revert changes to default style in boxplot
> - #2941 / #3012 calling cla() in `set_ticks_position`
> - #2945 issues with hist, patch in issue
> - #2977 pyqt string validation (patch in issue)
>
> Bug PRs that need minor work:
> - #1981 / #2662 mark-every upgrade
> - #2150 / #2942 fixing issues with auto-limit + 0 height bar plots
> - #2394 / #2951 issues in mpl_toolkits.axes_grid1.anchored_artists
> - #2475 / #2843 contour labels (release critical)
> - #3000 / #3017 multi-line in pgf
>
> Bug PRs that need major work:
> - #1012, animation related PR from jdh.
> - #2366 / #2738 errorbar + linestyle (this is one of mine, Eric does
> not like it)
> - #2828 / #2927 issue with mutable objects, ==, and hash
>
>
> Documentation:
> - #2350 annotation arrow example, code in issue needs PR
> - #2742 how to do a re-base (mine, needs work)
> - #2796 offset on default formatter documentation
> - #2603 suggested edit in issue
> - #2908 404 in docs
> - #2918 re-write contribution guide lines to match reality
> - #2929 doc about clip-on
> - #2999 install documentation
> - #3004 remove all references to nxutils
> - #3035 documentation in Polygon object
> - #3055 maybe add warning to get_window_extent
>
> PRs that need review:
> - #2288 / #3053
> - #2602 / #3015 fix stem plots
> - #2822 (documentation clarification)
> - #2952 / #2518 turn off clipping on all pie charts
>
> feature PRs that need minor work:
> - #2855 adds flag to spy, pep8 issue
> - #2541 / 2874 fixes mouse over text in polar mode (rebase)
> - #2961 3D quiver
> - #2996 violin plots
>
> No idea what to do with
> - #2025, tkagg + osx framework build stuff
>
> Maybe resolved:
> - issues with the screen not matching the saved images (#1441, #2935,
> #2831, and #2889) might all be fixed by #3054
>
> I think I am going to start just doing merges with CHANGELOG conflicts
> on my local computer and pushing to matplotlib/master as the amount of
> re-bases we end up needing is getting absurd.
Maybe this problem could be reduced by having a directory for CHANGELOG 
chunks, one file per PR, with the PR number as the filename. Then at 
release time they could be concatenated, edited, appended to the real 
CHANGELOG, and deleted.
Another approach would be to have the CHANGELOG entry as an identifiable 
chunk in the commit message. Then they would be extracted and dealt 
with at release time, as above.
Eric
>
> Tom
>

Sorry for dropping the ball on moving things forward.
I would propose a feature freeze this weekend and the goal of getting
the first RC out by the end of the month. We should probably plan a
hangout sometime in between now and then if there is stuff we want to
work out at a lower latency.
There are 62 open issues tagged as 1.4.0, but there are a number of
issues which have both an issue and a PR so it is more like ~40 open
issues. At least some of these will probably be punted.
The major features that are outstanding and need work/discussion:
 - grid lines in polar plots (#1441, #1730, #1847, #2203
 - Qt5 (#2471) do we want to squeeze this in? ipython has it working
so I don't think it will be too bad (despite all the furry in that
issue).
 - turning down the garbage collection calls (#3045)
 - #2986 axes order for event handling
Bugs this still need patches:
 - auto-scale + sharex/sharey + aspect heuristics don't always work
(#1325, #2492). I could be convinced to punt this as it is 'fixed' by
just setting the limits by hand + the forcing parameters.
 - #2856 / #2900 issues with saving animations
 - #3065 font priority test failure
 - #2698 deal with empty lines in text + box
 + #3039 tornado should not be an install dependency
 + #3042 revert changes to default style in boxplot
 - #2941 / #3012 calling cla() in `set_ticks_position`
 - #2945 issues with hist, patch in issue
 - #2977 pyqt string validation (patch in issue)
Bug PRs that need minor work:
 - #1981 / #2662 mark-every upgrade
 - #2150 / #2942 fixing issues with auto-limit + 0 height bar plots
 - #2394 / #2951 issues in mpl_toolkits.axes_grid1.anchored_artists
 - #2475 / #2843 contour labels (release critical)
 - #3000 / #3017 multi-line in pgf
Bug PRs that need major work:
 - #1012, animation related PR from jdh.
 - #2366 / #2738 errorbar + linestyle (this is one of mine, Eric does
not like it)
 - #2828 / #2927 issue with mutable objects, ==, and hash
Documentation:
 - #2350 annotation arrow example, code in issue needs PR
 - #2742 how to do a re-base (mine, needs work)
 - #2796 offset on default formatter documentation
 - #2603 suggested edit in issue
 - #2908 404 in docs
 - #2918 re-write contribution guide lines to match reality
 - #2929 doc about clip-on
 - #2999 install documentation
 - #3004 remove all references to nxutils
 - #3035 documentation in Polygon object
 - #3055 maybe add warning to get_window_extent
PRs that need review:
 - #2288 / #3053
 - #2602 / #3015 fix stem plots
 - #2822 (documentation clarification)
 - #2952 / #2518 turn off clipping on all pie charts
feature PRs that need minor work:
 - #2855 adds flag to spy, pep8 issue
 - #2541 / 2874 fixes mouse over text in polar mode (rebase)
 - #2961 3D quiver
 - #2996 violin plots
No idea what to do with
 - #2025, tkagg + osx framework build stuff
Maybe resolved:
 - issues with the screen not matching the saved images (#1441, #2935,
#2831, and #2889) might all be fixed by #3054
I think I am going to start just doing merges with CHANGELOG conflicts
on my local computer and pushing to matplotlib/master as the amount of
re-bases we end up needing is getting absurd.
Tom
-- 
Thomas Caswell
tca...@gm...

I just wanted to let you know that there is currently a vacancy for a
full-time developer at the Met Office, the UK's National Weather Service,
within our Analysis, Visualisation and Data (AVD) team.
I'm posting on this list as the Met Office's AVD team are heavily involved
in the development of Python packages to support the work that our
scientists undertake on a daily basis. The vast majority of the AVD team's
time is spent working on our own open source Python packages Iris, cartopy
and biggus as well as working on packages such as numpy, scipy, matplotlib
and IPython; so we don't see this as just a great opportunity to work
within a world class scientific organisation, but a role which will also
deliver real benefits to the wider scientific Python community.
Please see http://goo.gl/3ScFaZ for full details and how to apply, or
contact HRE...@me... if you have any questions.
Many Thanks,
Phil

On Mon, May 12, 2014 at 10:31 AM, Benjamin Root <ben...@ou...> wrote:
> No, it gets used. We just have a huge backlog of issue tickets to go
> through.
>
> At first glance, I think this problem has already been reported and fixed in
> master. Can you try building from source the master branch on github and
> seeing if that fixes your problem?
Sorry, wasn't aware of the backlog.
Yes, I downloaded and built 1.4.x. That does seem to solve the problem.
Thanks!
Skip

No, it gets used. We just have a huge backlog of issue tickets to go
through.
At first glance, I think this problem has already been reported and fixed
in master. Can you try building from source the master branch on github and
seeing if that fixes your problem?
Cheers!
Ben Root
On Mon, May 12, 2014 at 9:24 AM, Skip Montanaro <sk...@po...> wrote:
> On Wed, May 7, 2014 at 9:04 AM, Skip Montanaro <sk...@po...> wrote:
> > I'm trying to use the webagg backend for the first time, and seem to
> > be bumping into a common problem - nothing appears.
>
> I'm guessing that the complete lack of response both here and on
> matplotlib-users means nobody uses the webagg backend?
>
> Skip Montanaro
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Wed, May 7, 2014 at 9:04 AM, Skip Montanaro <sk...@po...> wrote:
> I'm trying to use the webagg backend for the first time, and seem to
> be bumping into a common problem - nothing appears.
I'm guessing that the complete lack of response both here and on
matplotlib-users means nobody uses the webagg backend?
Skip Montanaro

To avoid code duplication you can also use the pypi package
https://pypi.python.org/pypi/ordereddict
Yaron
On 7 May 2014 18:14, Federico Ariza <ari...@gm...> wrote:
> Yes I know.
>
> But I don't want to pollute more than strictly necessary. There is already
> too much unused code around.
>
> Federico
> On 7 May 2014 11:12, "Nathaniel Smith" <nj...@po...> wrote:
>
>> It is also technically possible to use a drop-in fallback
>> implementation on older pythons, e.g.:
>> https://github.com/pydata/patsy/blob/master/patsy/compat.py#L120
>> https://github.com/pydata/patsy/blob/master/patsy/compat_ordereddict.py
>>
>> -n
>>
>> On Wed, May 7, 2014 at 4:03 PM, Federico Ariza <ari...@gm...>
>> wrote:
>> > Hello
>> >
>> > Working on the MEP22 I would like to use an OrderedDict but it is only
>> > natively available from python 2.7
>> >
>> > Are there any plans to remove 2.6 for matplotlib 1.5?
>> >
>> > If not. I will just use a list with dicts inside, not as elegant but
>> works.
>> >
>> > Thanks
>> > Federico
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Is your legacy SCM system holding you back? Join Perforce May 7 to find
>> out:
>> > &#149; 3 signs your SCM is hindering your productivity
>> > &#149; Requirements for releasing software faster
>> > &#149; Expert tips and advice for migrating your SCM now
>> > http://p.sf.net/sfu/perforce
>> > _______________________________________________
>> > Matplotlib-devel mailing list
>> > Mat...@li...
>> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> >
>>
>>
>>
>> --
>> Nathaniel J. Smith
>> Postdoctoral researcher - Informatics - University of Edinburgh
>> http://vorpus.org
>>
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find
> out:
> &#149; 3 signs your SCM is hindering your productivity
> &#149; Requirements for releasing software faster
> &#149; Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

It is also technically possible to use a drop-in fallback
implementation on older pythons, e.g.:
 https://github.com/pydata/patsy/blob/master/patsy/compat.py#L120
 https://github.com/pydata/patsy/blob/master/patsy/compat_ordereddict.py
-n
On Wed, May 7, 2014 at 4:03 PM, Federico Ariza <ari...@gm...> wrote:
> Hello
>
> Working on the MEP22 I would like to use an OrderedDict but it is only
> natively available from python 2.7
>
> Are there any plans to remove 2.6 for matplotlib 1.5?
>
> If not. I will just use a list with dicts inside, not as elegant but works.
>
> Thanks
> Federico
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> &#149; 3 signs your SCM is hindering your productivity
> &#149; Requirements for releasing software faster
> &#149; Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
-- 
Nathaniel J. Smith
Postdoctoral researcher - Informatics - University of Edinburgh
http://vorpus.org

Yes I know.
But I don't want to pollute more than strictly necessary. There is already
too much unused code around.
Federico
On 7 May 2014 11:12, "Nathaniel Smith" <nj...@po...> wrote:
> It is also technically possible to use a drop-in fallback
> implementation on older pythons, e.g.:
> https://github.com/pydata/patsy/blob/master/patsy/compat.py#L120
> https://github.com/pydata/patsy/blob/master/patsy/compat_ordereddict.py
>
> -n
>
> On Wed, May 7, 2014 at 4:03 PM, Federico Ariza <ari...@gm...>
> wrote:
> > Hello
> >
> > Working on the MEP22 I would like to use an OrderedDict but it is only
> > natively available from python 2.7
> >
> > Are there any plans to remove 2.6 for matplotlib 1.5?
> >
> > If not. I will just use a list with dicts inside, not as elegant but
> works.
> >
> > Thanks
> > Federico
> >
> >
> >
> ------------------------------------------------------------------------------
> > Is your legacy SCM system holding you back? Join Perforce May 7 to find
> out:
> > &#149; 3 signs your SCM is hindering your productivity
> > &#149; Requirements for releasing software faster
> > &#149; Expert tips and advice for migrating your SCM now
> > http://p.sf.net/sfu/perforce
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
>
>
>
> --
> Nathaniel J. Smith
> Postdoctoral researcher - Informatics - University of Edinburgh
> http://vorpus.org
>

Hello
Working on the MEP22 I would like to use an OrderedDict but it is only
natively available from python 2.7
Are there any plans to remove 2.6 for matplotlib 1.5?
If not. I will just use a list with dicts inside, not as elegant but works.
Thanks
Federico

Apologies for those of you seeing this for a second time. I've
received no response on matplotlib-users, so I'm turning to the
experts.
In one message, I wrote:
 I'm trying to use the webagg backend for the first time, and seem to
 be bumping into a common problem - nothing appears. The first time I
 tried, I got a complaint that tornado was missing, so I installed it.
 After that, I get to try plotting. Here's my example:
 >>> import matplotlib
 >>> matplotlib.use('webagg')
 >>> import matplotlib.pyplot as plt
 >>> plt.plot(range(10))
 [<matplotlib.lines.Line2D object at 0x2f56690>]
 >>> plt.show()
 Created new window in existing browser session.
 Press Ctrl+C to stop server
 ^CServer stopped
 When I execute plt.show(), a new tab opens in my browser (Chrome, on
 Linux) with this URL: http://127.0.0.1:8988. That page has a single
 link (text: "Figure 1"). If I click that link, I get this URL:
 http://127.0.0.1:8988/1, but nothing appears. The page source contains
 a bunch of JavaScript references. For instance:
 <script src="/_static/jquery/js/jquery-1.7.1.min.js"></script>
 <script src="/_static/jquery/js/jquery-ui.min.js"></script>
 <script src="/_static/mpl.js"></script>
 <script src="/1/mpl_interface.js"></script>
 I see those JavaScript files at appropriate places in the
 .../backends/web_backend directory. What am I missing?
then followed that up with a bit more information:
 I tried this at home on my Mac. Tornado was already installed, so I
 updated it to 3.2.1, and ran a Matplotlib app I have which allows me
 to set the backend on the command line. I get the exact same behavior
 as at work on my Linux desktop. I get a page at 127.0.0:8988 with a
 "Figure 1" link. Clicking that takes me to 127.0.0.1:8988/1, which is
 a blank page.
 Chrome is my default web browser on both Linux and the Mac. I manually
 visited the page from both Firefox and Safari, clicked the link,
 and... nothing. The same behavior as on Chrome.
 Then I had the bright idea to look at the JavaScript console. It shows
 this error message:
 Uncaught SyntaxError: Unexpected token &
 Clicking that error took me to this line:
 var fig = new figure(&#39;1&#39;, websocket_url_prefix);
 Are those entities supposed to be '1'? What bit of code generates
 that JavaScript?
Can someone provide a bit of direction? I can't find the code that
generates the above snippet of JavaScript, but Chrome, at least,
doesn't like it.
Thx,
Skip

This is probably related to some of the random 'out of memory' errors
we have been getting on travis.
Maybe we should add `gc.collect` to the clean up method?
On Mon, May 5, 2014 at 7:15 AM, Jens Nielsen <jen...@gm...> wrote:
> I can confirm that after running the test suite with matplotlib.test() on a
> OSX 10.9 machine I end up with using around 1.5 Gb of memory. Furthermore
> the Python console that the tests are running from is extremely slow after
> the tests. Doing a gc.collect() frees most of the memory and returns the
> console to normal. I have only tested this with the stable 1.3.1 release
>
> /Jens
>
>
> On Sun, May 4, 2014 at 9:38 PM, Eric Firing <ef...@ha...> wrote:
>>
>> 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
>>
>>
>> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos. Get
>> unparalleled scalability from the best Selenium testing platform
>> available.
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> &#149; 3 signs your SCM is hindering your productivity
> &#149; Requirements for releasing software faster
> &#149; Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
-- 
Thomas Caswell
tca...@gm...