[matplotlib-devel] 1.2.0rc2 is tagged and uploaded

I have tagged and created a tarball for 1.2.0rc2. The githash is 656c88f3e546. The tarball is on the github download page here: https://github.com/matplotlib/matplotlib/downloads This includes a number of important bugfixes, including things required for creating Macintosh and Windows binarie

Re: [matplotlib-devel] 1.2.0rc1 is cut

Thanks for this. I think it makes sense to see if we can get to the bottom of this before putting out another release candidate. I have a feeling that the solution might be obvious to an Objective C expert -- which I am not. Mike On 09/17/2012 03:34 PM, Russell E. Owen wrote: > In article >

Re: [matplotlib-devel] 1.2.0rc1 is cut

On 09/17/2012 07:45 AM, Phil Elson wrote: Eric/Russell, is there an issue on github for the reported problem? Based on Christoph's comments, and couple of bugs I have just tracked down, it sounds like we could do with a RC2 soon-ish. The calendar states RC2 will be the 8th of October. Is it w

Re: [matplotlib-devel] 1.2.0rc1 is cut

On 09/16/2012 12:26 PM, Sandro Tosi wrote: > Hi Michael, > > On Wed, Sep 12, 2012 at 4:44 PM, Michael Droettboom wrote: >> I have tagged and created a tarball for 1.2.0rc1. The githash is >> bda6dd9feab8. The tarball is on the github download page here: >> >&

[matplotlib-devel] 1.2.0rc1 is cut

I have tagged and created a tarball for 1.2.0rc1. The githash is bda6dd9feab8. The tarball is on the github download page here: https://github.com/matplotlib/matplotlib/downloads I have created a new branch, v1.2.x, for continuing 1.2.x development. The feature freeze on master is now lifte

Re: [matplotlib-devel] Release Candidate

On 09/10/2012 12:49 PM, Mark Lawrence wrote: > My offer to test on Windows still holds. The question is test what? > Assuming that the intent is to support Python 2.6/7 and 3.1/2/3 then > different versions of Visual Studio are needed as detailed here > http://bugs.python.org/issue13210. I can't

Re: [matplotlib-devel] Release Candidate

important deadlines coming up soon, but I might be able to clean up the whole code. Thanks, N On 10 September 2012 18:00, Michael Droettboom <mailto:md...@stsci.edu>> wrote: Today is the scheduled day for release candidate 1.2rc1. We seem to be in really good shape. Thanks t

[matplotlib-devel] Release Candidate

Today is the scheduled day for release candidate 1.2rc1. We seem to be in really good shape. Thanks to everyone that has been working so hard to squash bugs, particularly ones that turned out to be bottomless rabbit holes. We have a few outstanding issues, which I'll categorize below: Critica

[matplotlib-devel] Is anyone using make.osx?

There is a discussion in a pull request about whether it is still needed. https://github.com/matplotlib/matplotlib/issues/751 It would be nice to have one obvious way to build on OS-X, so it makes sense to remove this file in that case. However, I thought it might be worth casting this questio

Re: [matplotlib-devel] idea for a matplotlib figure contest (in memoriam John Hunter)

Yes, this is a great idea, and I think SciPy is a great forum for it. I'll coordinate with next year's organizers and see if we can't add this as a new category along with the paper submissions. Mike On 08/30/2012 04:58 AM, Phil Elson wrote: What a great idea! Perhaps we could arrange judging

Re: [matplotlib-devel] Transforms bug

I'm not sure this is a bug. The transformation is being applied in data space, and then the mapping to physical space is not square in the x and y dimensions. I think calling set_aspect('equal') on the axes should fix this -- if it doesn't, that's indeed a bug. Mike On 08/27/2012 01:05 PM, D

[matplotlib-devel] Feature freeze progress

As of now, we have 14 issues on the 1.2.x milestone, plus 6 issues on the 1.2.x known bugs milestone. Since there's still a lot of work to be done on these before the rc1, I'm thinking I will continue to hold off on creating a 1.2.x branch. (Creating the branch would mean all of the pending PR

Re: [matplotlib-devel] MEP10: Modernizing the documentation

On 08/26/2012 05:33 AM, Anton Akhmerov wrote: > Michael Droettboom writes: > >> >> >> Working with the documentation this past week has me a little >> frustrated with the state of it. Enough to write a MEP. > https://github.com/matplotlib

Re: [matplotlib-devel] Missing 1.1.1 tarball on PyPI

On 08/24/2012 09:31 AM, Damon McDougall wrote: > On Fri, Aug 24, 2012 at 09:03:48AM -0400, Michael Droettboom wrote: >> Sorry about that. PyPI is a bear. >> >> It seems to finally be uploaded correctly, and "pip install >> matplotlib" is working for me. Can

Re: [matplotlib-devel] Missing 1.1.1 tarball on PyPI

Sorry about that. PyPI is a bear. It seems to finally be uploaded correctly, and "pip install matplotlib" is working for me. Can you please confirm? Mike On 08/24/2012 05:23 AM, Ludwig Schwardt wrote: Hi, There does not seem to be an actual tarball of matplotlib 1.1.1 on PyPI at http://p

Re: [matplotlib-devel] Two 1.2 milestones

on't envisage the milestone to be a longterm thing, but I do think its helpful to separate them from things we definitely want to resolve before taking a 1.2.x cut. I would be happy even if we delete the milestone first thing after the freeze tomorrow. Regards, Phil On 19 August 2012 1

Re: [matplotlib-devel] Two 1.2 milestones

On 08/19/2012 01:38 PM, Damon McDougall wrote: > On Sun, Aug 19, 2012 at 12:58:53PM -0400, Michael Droettboom wrote: >> There seems to be a new milestone "1.2.x known bugs". Is there a good >> reason to have two milestones for 1.2? As we enter into the freeze >> ph

[matplotlib-devel] 1.2 Feature freeze plans for tomorrow

There has been a lot of great work triaging and fixing bugs lately. This release is going to see more new features and bugfixes than we've seen in matplotlib in a long time. Thanks to everyone! Here's my plan for tomorrow's feature freeze: Let's try to get a handle on the PRs we have for 1.2.

[matplotlib-devel] Two 1.2 milestones

There seems to be a new milestone "1.2.x known bugs". Is there a good reason to have two milestones for 1.2? As we enter into the freeze phase for 1.2, it would be easier to just track a single milestone. Mike -- Live

[matplotlib-devel] MEP10: Modernizing the documentation

Working with the documentation this past week has me a little frustrated with the state of it. Enough to write a MEP. https://github.com/matplotlib/matplotlib/wiki/Mep10 In particular, it would be nice to compile a list of concerns about the docstrings and documentation layout so that we can

Re: [matplotlib-devel] MEP9: interactivity

Here's my initial thoughts: There are a few examples in the event_handling that are going to be much simplified by this new infrastructure. They should be updated to point people in the direction of this new/better/easier way. How do the *select* methods relate to the existing pick functiona

Re: [matplotlib-devel] MEP9: interactivity

Thanks for this. The first "real" MEP! My view is that we can discuss this here, and then you would be ultimately responsible for updating the MEP based on feedback -- but this is a new process, we can be as flexible as we want. I've read it through once and think it's a very valuable idea i

Re: [matplotlib-devel] How to properly use git to implement a feature

On 08/12/2012 09:34 PM, Daniel Hyams wrote: I was wanting to add a feature to matplotlib...one that I would use in my application. I also want to contribute the feature back. I'm personally using version 1.1.1 of matplotlib. Disclaimer...I only know enough about git to be dangerous. So is

Re: [matplotlib-devel] matplotlib.github.com

On 08/10/2012 03:45 PM, Fernando Perez wrote: > On Fri, Aug 10, 2012 at 7:26 AM, Michael Droettboom wrote: >> Supporting existing links to matplotlib.sourceforge.net is of course >> very important, and I would put whatever redirects we need to keep those >> working in any e

Re: [matplotlib-devel] matplotlib.org

hanks > for doing that! You're welcome! Mike > > > > On 10 August 2012 15:28, Michael Droettboom wrote: >> I have registered matplotlib.org. It currently just points to >> matplotlib.sourceforge.net, but it will allow us to have a consistent >> URL

[matplotlib-devel] matplotlib.org

I have registered matplotlib.org. It currently just points to matplotlib.sourceforge.net, but it will allow us to have a consistent URL that isn't dependent on any particular host going forward. Mike -- Live Security V

[matplotlib-devel] matplotlib.github.com

I know we had experimented with moving the main documentation website to matplotlib.github.com a while ago (and in fact there's still an old version of the docs sitting there). I can't remember the reason we chose to remain at matplotlib.sourceforge.net and searching the mailing list archive i

[matplotlib-devel] Client-side plotting

For anyone who's interested, I've started blogging about my initial thinking on client-side plotting in the web browser with matplotlib here: http://mdboom.github.com/ (I hope to get this aggregated into planet.scipy.org soon, too). Mike

Re: [matplotlib-devel] bad link on matplotlib website

On 08/06/2012 02:10 PM, Benjamin Root wrote: On Tue, Dec 6, 2011 at 4:15 PM, Jim Hunziker > wrote: I'm not sure if this is the right place to report this, but the link to Python(x, y) on http://matplotlib.sourceforge.net/users/installing.html points to a

[matplotlib-devel] Introducing MEPs

As I alluded to yesterday, I think it's time to start formalizing, ever so slightly, the process to get larger chunks of work done on the code base. Therefore, I propose the concept of "matplotlib enhancement proposals" to track this work. I've created a simple "MEP template" on the wiki, and

[matplotlib-devel] matplotlib events calendar

I have created a Google Calendar for tracking release schedule dates. This may also include other matplotlib-related events in the future. At the moment, this includes the dates John outlined for the next release. The URLs for subscribing to the calendar are on the wiki here: https://github.c

Re: [matplotlib-devel] [Matplotlib-users] ANN: Michael Droettboom, matplotlib lead developer

he first release to support Python 3.x. Exciting times. Details to follow in another e-mail thread. John, thanks again for the honor and I hope I can follow your example of leadership. They are big shoes to fill. Mike On 08/02/2012 05:25 PM, John Hunter wrote: It is a great honor for

Re: [matplotlib-devel] bugs/difficulties encountered while creating interactive SVG

On 07/29/2012 11:33 AM, Dimitrios Apostolou wrote: >> -- >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respo

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

I don't think this has anything to do with matplotlib, but instead just with pygobject (or perhaps just gtk itself) on Fedora 17. I suspect that this fedora bug is responsible: https://bugzilla.redhat.com/show_bug.cgi?id=790053 Importing gtk is enough to produce this warning: In [1]: import g

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On 06/13/2012 01:29 PM, Benjamin Root wrote: On Mon, Jun 11, 2012 at 2:23 PM, Michael Droettboom <mailto:md...@stsci.edu>> wrote: On 06/11/2012 02:17 PM, John Hunter wrote: > On Mon, Jun 11, 2012 at 10:30 AM, Michael Droettboommailto:md...@stsci.edu>> wrote:

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

On 06/11/2012 02:17 PM, John Hunter wrote: > On Mon, Jun 11, 2012 at 10:30 AM, Michael Droettboom wrote: >> John: Do you know which git revision you made the tarballs from? I'll go >> ahead and tag it. > https://github.com/matplotlib/matplotlib/commit/97f713098a71c70d7

Re: [matplotlib-devel] v1.1.1rc2 tarballs are up

John: Do you know which git revision you made the tarballs from? I'll go ahead and tag it. Mike On 06/09/2012 09:52 PM, Benjamin Root wrote: Don't forget to tag the rc in git! On Sat, Jun 9, 2012 at 6:40 PM, John Hunter > wrote: On Sat, Jun 9, 2012 at 5:33 PM,

Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)

I also want to flag PR #934 as something that should go into the rc. It's currently against master but it's important enough/simple enough that it should be backported. Mike On 06/07/2012 03:04 PM, John Hunter wrote: > On Thu, Jun 7, 2012 at 1:55 PM, Eric Firing wrote: > >> I did not see any

Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)

On 06/07/2012 05:44 PM, Eric Firing wrote: > On 06/07/2012 09:04 AM, John Hunter wrote: >> On Thu, Jun 7, 2012 at 1:55 PM, Eric Firing wrote: >> >>> I did not see any replies to Sandro's reasonable question. >>> >>> Wasn't there at least a plan for a 1.1.x release soon? >>> >>> There are quite a

Re: [matplotlib-devel] PR backlog -- ping us!

y PR will have to wait until tonight, unfortunately) > -paul > > On Fri, Jun 1, 2012 at 8:37 AM, Michael Droettboom wrote: >> As you probably know, we've got a lot of pull requests in the hopper. >> Thanks to everyone who's been triaging these lately. >> >> I

[matplotlib-devel] PR backlog -- ping us!

As you probably know, we've got a lot of pull requests in the hopper. Thanks to everyone who's been triaging these lately. I've just gone through and tried to add comments about what's left to be done with each to make them mergeable. (9 times out of 10, I'm saying "add an example and unit te

[matplotlib-devel] Need some OS-X and Windows testing

Just wanted to draw attention to some platform-specific pull requests that need some third-party testing and comments from people on OS-X and MS-Windows. If you're running on one of those platforms and able to build from git branches, it would be great to have some input: OS-X: Updates to t

Re: [matplotlib-devel] Added Phil Elson as a developer

On 05/31/2012 11:16 AM, Benjamin Root wrote: On Thu, May 31, 2012 at 7:55 AM, John Hunter > wrote: Phil Elson has been making pull requests for some time now on matters great and small, from hairy transformations improvements to minor docstring cleanups t

Re: [matplotlib-devel] python 3 fork?

irectory (in my source location) everything works. Tom On May 30, 2012, at 2:40 PM, Michael Droettboom wrote: > On 05/30/2012 03:32 PM, Thomas Kluyver wrote: >> On 30 May 2012 20:05, Tom Lippman wrote: >>> I'm on OS X 10.7, using the python 3.2 >> I saw someon

Re: [matplotlib-devel] python 3 fork?

On 05/30/2012 03:32 PM, Thomas Kluyver wrote: > On 30 May 2012 20:05, Tom Lippman wrote: >> I'm on OS X 10.7, using the python 3.2 > I saw someone recently who'd managed to get it built for Python 3 on > OS X. I suggested he come here to help simplify the process - this is > what he did: http://st

Re: [matplotlib-devel] python 3 fork?

The git master is compatible with Python 3, but it has not made it into a release. Will be making at least one more 1.1.x bugfix release which will support Python 2.4 - 2.7 before making the next major release which will support Python 2.6 - 3.2. Mike On 05/30/2012 02:49 PM, Tom Lippman wro

Re: [matplotlib-devel] 'NoneType' object has no attribute 'endswith' when running tests in a chroot

On 05/20/2012 12:51 PM, Sandro Tosi wrote: Hello, I've been trying to fix this problem for hours, and it's getting me mad but to no conclusion, so I'm asking here. In Debian we build our packges in a chroot, with all the minimum dependecies needed to build the package (to guarantee reproducibili

Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)

On 05/14/2012 12:58 PM, Christoph Gohlke wrote: > > On 5/14/2012 7:43 AM, Michael Droettboom wrote: >> On 05/12/2012 01:33 PM, Christoph Gohlke wrote: >>> >>> On 5/12/2012 6:16 AM, Michael Droettboom wrote: >>>> On 05/12/2012 07:21 AM, Mark Lawrence wr

Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)

On 05/12/2012 05:56 AM, Sandro Tosi wrote: > Hello, > as you may be aware of, in 1 month (more or less) Debian will freeze, > that means that no new upstream releases will be allowed in the > upcoming release, only fixex for important bugs. > > Currently in Debian archive we have 1.1.1rc1 . Recent

Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)

On 05/12/2012 01:33 PM, Christoph Gohlke wrote: On 5/12/2012 6:16 AM, Michael Droettboom wrote: On 05/12/2012 07:21 AM, Mark Lawrence wrote: My original offer (made several months ago) to help test this on Windows still stands :) Thanks. Does git master build and pass the unit tests on

Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)

On 05/12/2012 07:21 AM, Mark Lawrence wrote: > > My original offer (made several months ago) to help test this on Windows > still stands :) > Thanks. Does git master build and pass the unit tests on Windows? Mike -- Live

Re: [matplotlib-devel] switching rc files (and discussion of styles)

The minimum requirement of the 1.1 series is still Python 2.4, believe it or not, though I'm not sure practically what the minimum numpy is. The next major release (which will include Python 3 support) bumps the minimum requirement up to Python 2.6. Mike On 05/11/2012 05:32 PM, Warren Weckes

Re: [matplotlib-devel] bug in font display using png backend

Git bisect shows that this was introduced in f57dddc20625. Looking at the github comments for that commit: https://github.com/matplotlib/matplotlib/commit/f57dddc20625809436956675d23b09baddcc9e0e strange enough the problem and solution are already discussed, it just seems the solution never m

Re: [matplotlib-devel] soliciting feedback on proposed user survey

This is a great idea. A question that might be worth adding is what backends are being used. I'd be interested to find out which ones are most heavily used. A related question (though I don't know how easy it would be to be complete on) would be what plot types are used. Thanks for doing thi

Re: [matplotlib-devel] 1.1.1rc RuntimeError: underlying C/C++ object has been deleted

Can you provide more detail about how to reproduce this? I can deduce you're using the Qt4Agg backend -- but running simple_plot.py, zooming around, and then closing the window does not seem to reproduce the error here. What version of Qt/PyQt/PySide are you running. What platform? Mike On 0

Re: [matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

I just put a pull request up that resolves these tests for me: #779. If it's working for others, we should go ahead and merge that into v1.1.x before the release. Mike On 03/20/2012 09:49 AM, Michael Droettboom wrote: We seem to have a large number of failing tests due to the recent

Re: [matplotlib-devel] test images update

Have a look at #779. Can you let me know if this resolves the tests for you? https://github.com/matplotlib/matplotlib/pull/779 Mike On 03/20/2012 09:48 AM, Michael Droettboom wrote: I've mainly done this using a thumbnailing tool like gthumb on one side of the screen and a console to

Re: [matplotlib-devel] matplotlib v1.1.1 (bugfix) rc1 on Thursday

We seem to have a large number of failing tests due to the recent fixes to the snapping behavior. Mainly these just need to be triaged and have the baseline images replaced. I'm going to see how far I get on this today. Mike On 03/19/2012 01:58 PM, John Hunter wrote: I think we are pretty cl

Re: [matplotlib-devel] test images update

I've mainly done this using a thumbnailing tool like gthumb on one side of the screen and a console to copy files on the other. Since the diff images are already generated, it's generally not so bad. I'm going to try to get all tests passing before the release if possible. Wish me luck. :)

Re: [matplotlib-devel] Is snapping still right?

Assuming there's no bugs, this doesn't look like the kind of thing that the snapping algorithm would cause or address. Snapping is only supposed to kick in when the lines are rectilinear (i.e. perfectly horizontal or vertical) which none of the lines in this plot appear to be. This plot actua

Re: [matplotlib-devel] Pyplot Documentation

That would be great! There's always room for improvement in the docs. The best way you can help is to read up on how to generate github pull requests (in the matplotlib developer docs) and start submitting proposals for things that could be improved. Cheers, Mike On 02/29/2012 05:47 PM, S K

Re: [matplotlib-devel] Non string projections

Thanks for doing this work. On 02/03/2012 11:40 AM, Phil Elson wrote: > Currently, one can set the theta_0 of a polar plot with: > > ax = plt.axes(projection='polar') > ax.set_theta_offset(np.pi/2) > ax.plot(np.arange(100)*0.15, np.arange(100)) > > But internally there are some nasties going on (t

Re: [matplotlib-devel] imread() in master branch doesn't work

ill a good idea, but I think that > is now an independent question. > > Eric > > > On 01/17/2012 05:37 AM, Michael Droettboom wrote: >> I can't confirm this on RHEL5 64-bit or Fedora 16 64-bit. >> >> Have you tried removing the build and installed directories and &

Re: [matplotlib-devel] imread() in master branch doesn't work

; Eric > > -- > RSA(R) Conference 2012 > Mar 27 - Feb 2 > Save $400 by Jan. 27 > Register now! > http://p.sf.net/sfu/rsa-sfdev2dev2 > ___ > Matplotlib-de

Re: [matplotlib-devel] RectangleSelector

On 01/05/2012 02:22 AM, Benjamin Root wrote: > > I don't have an opinion on this yet, but I do want to note that if this change were applied, then the lasso selector should probably also be changed in order to be consistent. I believe the lasso selector already does this (determined experi

Re: [matplotlib-devel] [Matplotlib-users] contourf with rgba colours

I think I've discovered the root of this problem. A change was made during the 1.1.x cycle to tell Agg that we're giving it premultiplied alpha in the image data (see commit 1dac36d829). This made displaying images loaded from files that had an alpha channel work correctly and made it consist

Re: [matplotlib-devel] RectangleSelector

This is a great fix. Would you mind submitting it as a github pull request so we can review it there? Mike On 01/05/2012 01:20 AM, Arnaud Gardelein wrote: > In my configuration, when button is released out of the axes, > RectangleSelector does not catch the release-button event. The rectangle >

Re: [matplotlib-devel] Merging v1.1.x to master?

s array to avoid side effects; fixes issue #625 > > commit 3c3c466564cba3d80f928a46857e54738787779b > Merge: 96caca8 fb52b96 > Author: Michael Droettboom > Date: Wed Dec 14 06:10:26 2011 -0800 > > Merge pull request #586 from mdboom/numpy-version-13 > > Numpy version 1.4 > > commit 585606

Re: [matplotlib-devel] jsxgraph or flot backend (or interactive viewer for svg backend?)

On 12/15/2011 11:44 PM, Jason Grout wrote: > On 12/15/11 8:03 PM, Michael Droettboom wrote: >> On 12/07/2011 11:36 PM, Jason Grout wrote: >>> On 12/7/11 10:27 PM, Chris Barker wrote: >>>> On 12/5/11 9:49 PM, Jason Grout wrote: >>>>> Has anyone ever

Re: [matplotlib-devel] jsxgraph or flot backend (or interactive viewer for svg backend?)

> approach is interactive zooming of plots within the browser. If this >> is >>> not important to you, it will probably be faster to generate static >> PNGs >> > or SVGs. >>> >>> The HTML5 backend should be easy to try

[matplotlib-devel] Gtk3/GObject-introspection support in master

Thanks to the great work of Robert Johannson, we now have Gtk3 support using the GObject introspection Python bindings. To use, set your backend to "Gtk3Cairo" or "Gtk3Agg". It seems to be working well, but it would be great to get testing on a broader set of platforms etc. Unfortunately, t

Re: [matplotlib-devel] v1.1.x branch was (temporarily) wrong

On 12/06/2011 10:10 PM, Benjamin Root wrote: On Tuesday, December 6, 2011, Michael Droettboom <mailto:md...@stsci.edu>> wrote: > Yesterday I managed to accidentally move the v1.1.x branch pointer to > point to master. I have since moved it back, but you may need to rebase &g

[matplotlib-devel] v1.1.x branch was (temporarily) wrong

.x Mike -- Michael Droettboom Science Software Branch Space Telescope Science Institute Baltimore, Maryland, USA -- Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a

Re: [matplotlib-devel] nxutils

b.inside_poly to use Path instead and will submit it later today. --James *From:*Michael Droettboom [mailto:md...@stsci.edu] *Sent:* Friday, November 18, 2011 6:23 AM *To:* matplotlib-devel@lists.sourceforge.net *Subject:* Re: [matplotlib-devel] nxutils Perhaps another alternative is to

Re: [matplotlib-devel] nxutils

Perhaps another alternative is to just include a small compatibility module that would call the new functionality under the hood. Mike On 11/18/2011 09:07 AM, Michael Droettboom wrote: nxutils has been removed from master because it is completely redundant to the Path functionality that has

Re: [matplotlib-devel] nxutils

points_inside_poly? And, if I remember right, Path uses that to calculate contains(). Ben Root On Thursday, November 17, 2011, Eric Firing <mailto:efir...@hawaii.edu>> wrote: > On 11/17/2011 10:19 AM, Michael Droettboom wrote: >> Most of what was in nxutils has been superseded by things i

Re: [matplotlib-devel] nxutils

Most of what was in nxutils has been superseded by things in Numpy, and it makes more sense for it to be over there. In the case of points_inside_poly, you can use the Path object in path.py and the "contains_point" method. Mike On 11/17/2011 12:03 PM, James Evans wrote: All, I have not t

Re: [matplotlib-devel] Heads-up: master badly broken, syntaxerror in setup.py

This should now be fixed. Mike On 11/17/2011 02:40 AM, Jens Nielsen wrote: > It works in python3 > > The python statement in python2.7 (and 2.6) does not support the end argument. > Adding a "from __future__ import print_function" to the beginning of > setup.py seems to fix it. > > Greetings Jens

Re: [matplotlib-devel] GTK3 backend for matplotlib?

ling list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -- Michael Droettboom Science Software Branch Space Telescope Science Institute Baltimore, Maryland, USA -- RS

[matplotlib-devel] Py3 merge

I just pressed the big green merge button... :) Master should now have all of the Python 3 portability changes. It's passing all tests, and running all examples, but I still wouldn't be surprised if some things broke in the process. Please kick the tires and report bugs. It would be helpful

Re: [matplotlib-devel] matplotlib.pyplot.imsave bug

http://p.sf.net/sfu/android-dev2dev ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -- Michael Droettboom Science Software Branch Space Telescope Science

Re: [matplotlib-devel] Merging Python 3 branch?

--ext-diff upstream/master mdboom/py3-merge Of course, we can't use github's code review features that way :( Mike On 10/31/2011 09:16 AM, Michael Droettboom wrote: The pull request to merge the py3 fork back into matplotlib/master is here: https://github.com/matplotlib/matplotli

Re: [matplotlib-devel] Merging Python 3 branch?

The pull request to merge the py3 fork back into matplotlib/master is here: https://github.com/matplotlib/matplotlib/pull/565 Thanks to everyone who worked on it. I plan to leave this up for a while and get as much chance for review as possible. Mike On 10/28/2011 01:50 PM, Michael

Re: [matplotlib-devel] Merging Python 3 branch?

Sorry for the double post. Having trouble with my mail transport today. The one with the later date is the "canonical reference". :) -- The demand for IT networking professionals continues to grow, and the demand for s

Re: [matplotlib-devel] Merging Python 3 branch?

On 10/28/2011 02:41 PM, Eric Firing wrote: > On 10/28/2011 07:50 AM, Michael Droettboom wrote: >> Now that we have 1.1.0 out, I was thinking maybe now is the time to >> merge the matplotlib-py3 branch into master. As a reminder, the main >> downside is losing compatibilit

Re: [matplotlib-devel] Merging Python 3 branch?

On 10/28/2011 02:41 PM, Eric Firing wrote: > On 10/28/2011 07:50 AM, Michael Droettboom wrote: >> Now that we have 1.1.0 out, I was thinking maybe now is the time to >> merge the matplotlib-py3 branch into master. As a reminder, the main >> downside is losing compatibilit

[matplotlib-devel] Merging Python 3 branch?

Now that we have 1.1.0 out, I was thinking maybe now is the time to merge the matplotlib-py3 branch into master. As a reminder, the main downside is losing compatibility with Python 2.5 and earlier. We would continue to have a 1.1.x maintenance branch for the foreseeable future for small-yet-

Re: [matplotlib-devel] Possible bug in matplotlib.cbook.CallbackRegistry

Another common solution to this problem is to copy the list of callbacks before iterating over it. Having a simple example would be helpful here so we can experiment with these alternate approaches. Mike On 10/16/2011 09:04 PM, to...@i3dtech.com wrote: > Within matplotlib.cbook.CallbackRegistr

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On 10/06/2011 10:46 AM, John Hunter wrote: > On Thu, Oct 6, 2011 at 9:44 AM, John Hunter wrote: >> On Thu, Oct 6, 2011 at 9:17 AM, Michael Droettboom wrote: >> >>> Pretty simple. I have a pull request here: >>> >>> https://github.com/matplotlib/matp

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On 10/06/2011 09:33 AM, Michael Droettboom wrote: > On 10/05/2011 05:17 PM, John Hunter wrote: >> On Wed, Oct 5, 2011 at 1:49 PM, Eric Firing wrote: >> >>> Sorry to be holding things up after having nagged about getting a >>> release out, but I just now marked #

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On 10/05/2011 05:17 PM, John Hunter wrote: > On Wed, Oct 5, 2011 at 1:49 PM, Eric Firing wrote: > >> Sorry to be holding things up after having nagged about getting a >> release out, but I just now marked #506 "release_critical". It looks >> like a pretty fundamental bug in blitting on qt4agg, an

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On 10/05/2011 03:38 AM, Sandro Tosi wrote: > On Tue, Oct 4, 2011 at 20:00, Michael Droettboom wrote: >> As for your bug, it seems there is a bug in how the plot_formats commandline >> argument is parsed. Could you please try this branch and let me know if it >> resolves t

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

ranch and let me know if it resolves the issue? https://github.com/mdboom/matplotlib/tree/doc_build_fail Mike On 10/04/2011 10:50 AM, Michael Droettboom wrote: I'm looking into this. It seems there's a pretty straightforward-to-fix bug parsing the commandline arguments. Beyond that

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -- Michael Droettboom Science Software Branch Space Telescope Sc

Re: [matplotlib-devel] propose 1.1.0 release tomorrow

On 10/03/2011 01:01 PM, Benjamin Root wrote: On Mon, Oct 3, 2011 at 7:54 AM, John Hunter > wrote: We made some additional progress over the weekend closing pull requests and issues, and I think we are ready to release tomorrow if no one objects. I want to h

Re: [matplotlib-devel] mpl release candidate branch

On 09/24/2011 03:33 PM, Jouni K. Seppänen wrote: > Jouni K. Seppänen writes: > >> Jouni K. Seppänen writes: >> >>> The light and condensed fonts are DejaVuSans, which happened to be >>> installed on the system on which that test was created. I think the test >>> should only rely on the fonts deli

Re: [matplotlib-devel] mpl release candidate branch

On 09/24/2011 08:22 AM, John Hunter wrote: > On Fri, Sep 23, 2011 at 5:04 PM, Benjamin Root wrote: >> Personally, my vote is to live with the deprecation warnings. They only >> happen if you turn warnings on in python 2.7 (by default, they are off). I >> am not that comfortable with such a chang

Re: [matplotlib-devel] mpl release candidate branch

I haven't seen any of these warnings: DeprecationWarnings and PendingDeprecationWarnings are supposed to be turned of by default in a vanilla Python build. However, I'm familiar with the PyCObject/PyCapsule issue from working on the matplotlib-py3 branch. The py3 branch has changes to the loc

Re: [matplotlib-devel] mpl release candidate branch

value that makes these pass on your machine. Mike On 09/23/2011 12:37 PM, John Hunter wrote: > On Fri, Sep 23, 2011 at 10:34 AM, Michael Droettboom wrote: >> I'm not able to reproduce this here (git/master on Ubuntu 10.4, Python >> 2.7). Can you send and/or link to an example br

Re: [matplotlib-devel] mpl release candidate branch

I'm not able to reproduce this here (git/master on Ubuntu 10.4, Python 2.7). Can you send and/or link to an example broken image? The way in which it is failing may illustrate the cause of the problem. It could also be that the difference in the freetype library/settings is causing enough di

<    1   2   3   4   5   6   7   8   9   10   >