[matplotlib-devel] Question about (local) developement workflow

Hi, i have a question about my personal developement workflow. I wanted to fix a bug in matplotlib, therefore i checked out the repository. Then i have to "install" matplotlib (with setupy.py build, setup.py install). But every time i chenged something, i have to reinstall mpl to test my changes.

Re: [matplotlib-devel] github devel question

Benjamin Root writes: > I am having difficulty completing a pull request that I opened. When I try > to merge the changes to upstream, they get rejected. I can merge it back to > my own master, and can even push it up to my github repo's master, but not > matplotlib's master. If you're followi

Re: [matplotlib-devel] What's the status of the py3k branch?

On 02/26/2011 02:37 AM, Eric Firing wrote: > On 02/25/2011 04:54 PM, Benjamin Root wrote: >> >> On Fri, Feb 25, 2011 at 8:01 PM, John Hunter> > wrote: >> >> >> >> >> >> On Feb 25, 2011, at 7:00 PM, Christoph Gohlke> > wrote: >> >>

Re: [matplotlib-devel] What's the status of the py3k branch?

> In any case it appears that with the exception of Tkinter, it may take a > long time before interactive mpl backends can be used with py3k. The MacOSX backend has already been ported to Py3k (at least the C part of it, which is the largest and most difficult part of it), though I won't be able

Re: [matplotlib-devel] What's the status of the py3k branch?

On 02/25/2011 08:00 PM, Christoph Gohlke wrote: > > On 2/25/2011 4:03 PM, Benjamin Root wrote: >> >> On Fri, Feb 25, 2011 at 5:11 PM, Paul Ivanov> > wrote: >> >> Fernando Garcia Bermudez, on 2011-02-03 09:14, wrote: >> > On Thu, Feb 3, 2011 at 06:05, Micha

Re: [matplotlib-devel] Question about (local) developement workflow

It sounds like you're doing it right. Make changes to the source directory, compile, then test. There are some ways to streamline this. One is to leave a terminal window or tab open just for compiling -- then each compile is just a matter of "up arrow, Enter". As an emacs user, I use the "c

Re: [matplotlib-devel] Question about (local) developement workflow

Maximilian Trescher writes: > Then i have to "install" matplotlib (with setupy.py build, setup.py > install). But every time i chenged something, i have to reinstall mpl to > test my changes. Unless you have something against setuptools (many people do): python setupegg.py develop This makes s

Re: [matplotlib-devel] What's the status of the py3k branch?

On 2/26/11 5:30 AM, Michiel de Hoon wrote: >> In any case it appears that with the exception of Tkinter, it may take a >> long time before interactive mpl backends can be used with py3k. > The MacOSX backend has already been ported to Py3k (at least the C part of > it, which is the largest and mos

Re: [matplotlib-devel] What's the status of the py3k branch?

On Sat, 26 Feb 2011 07:29:55 -0500, Michael Droettboom wrote: [clip] > Yes. The minimum version for this Python 3.x compatibility work is > Python 2.6. Anything earlier is just insane ;) Out of curiosity: did you consider using a single source tree for Python 2.x and 3.x, rather than a separate

Re: [matplotlib-devel] What's the status of the py3k branch?

On Sat, Feb 26, 2011 at 9:23 AM, Pauli Virtanen wrote: > On Sat, 26 Feb 2011 07:29:55 -0500, Michael Droettboom wrote: > [clip] >> Yes.  The minimum version for this Python 3.x compatibility work is >> Python 2.6.  Anything earlier is just insane ;) > > Out of curiosity: did you consider using a s

Re: [matplotlib-devel] Question about (local) developement workflow

On Saturday, February 26, 2011, Jouni K. Seppänen wrote: > Maximilian Trescher writes: > >> Then i have to "install" matplotlib (with setupy.py build, setup.py >> install). But every time i chenged something, i have to reinstall mpl to >> test my changes. > > Unless you have something against set

Re: [matplotlib-devel] Question about (local) developement workflow

> Even easier is > > python setupegg.py develop --user > > Which doesn't require sudo and is perfect for multiple-user systems. > I use for myself all the time. I installed the matplotlib developement version in a virtual environement, where you can install every package as user. Anyway, thanks

Re: [matplotlib-devel] What's the status of the py3k branch?

On 02/26/2011 02:30 AM, Michiel de Hoon wrote: >> In any case it appears that with the exception of Tkinter, it may take a >> long time before interactive mpl backends can be used with py3k. > > The MacOSX backend has already been ported to Py3k (at least the C part of > it, which is the largest a

Re: [matplotlib-devel] What's the status of the py3k branch?

Hi, On Sat, Feb 26, 2011 at 4:30 AM, Michiel de Hoon wrote: >> In any case it appears that with the exception of Tkinter, it may take a >> long time before interactive mpl backends can be used with py3k. > > The MacOSX backend has already been ported to Py3k (at least the C part of > it, which i

Re: [matplotlib-devel] What's the status of the py3k branch?

On Sat, Feb 26, 2011 at 8:51 AM, Darren Dale wrote: > On Sat, Feb 26, 2011 at 9:23 AM, Pauli Virtanen wrote: > > On Sat, 26 Feb 2011 07:29:55 -0500, Michael Droettboom wrote: > > [clip] > >> Yes. The minimum version for this Python 3.x compatibility work is > >> Python 2.6. Anything earlier is

Re: [matplotlib-devel] What's the status of the py3k branch?

On 02/26/2011 04:51 AM, Darren Dale wrote: > On Sat, Feb 26, 2011 at 9:23 AM, Pauli Virtanen wrote: >> On Sat, 26 Feb 2011 07:29:55 -0500, Michael Droettboom wrote: >> [clip] >>> Yes. The minimum version for this Python 3.x compatibility work is >>> Python 2.6. Anything earlier is just insane ;)

Re: [matplotlib-devel] What's the status of the py3k branch?

Hi, On Sat, Feb 26, 2011 at 6:23 AM, Pauli Virtanen wrote: > On Sat, 26 Feb 2011 07:29:55 -0500, Michael Droettboom wrote: > [clip] >> Yes.  The minimum version for this Python 3.x compatibility work is >> Python 2.6.  Anything earlier is just insane ;) > > Out of curiosity: did you consider usin

Re: [matplotlib-devel] git migration this weekend

On Wed, Feb 16, 2011 at 2:19 PM, Eric Firing wrote: > On 02/16/2011 08:38 AM, Darren Dale wrote: >> On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez   >> wrote: >>> are you guys planning on transfering the old bugs to github? >> >> Probably at some point. >> >>> As I >>> mentioned, I have code lyi

Re: [matplotlib-devel] git migration this weekend

On 02/26/2011 09:26 AM, Darren Dale wrote: > On Wed, Feb 16, 2011 at 2:19 PM, Eric Firing wrote: >> On 02/16/2011 08:38 AM, Darren Dale wrote: >>> On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez >>> wrote: are you guys planning on transfering the old bugs to github? >>> >>> Probably at s

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing wrote: > On 02/26/2011 09:26 AM, Darren Dale wrote: >> On Wed, Feb 16, 2011 at 2:19 PM, Eric Firing  wrote: >>> On 02/16/2011 08:38 AM, Darren Dale wrote: On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez     wrote: > are you guys planning

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 3:52 PM, Darren Dale wrote: > On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing wrote: >> On 02/26/2011 09:26 AM, Darren Dale wrote: >>> On Wed, Feb 16, 2011 at 2:19 PM, Eric Firing  wrote: On 02/16/2011 08:38 AM, Darren Dale wrote: > On Wed, Feb 16, 2011 at 12:39 PM,

Re: [matplotlib-devel] What's the status of the py3k branch?

On Sat, Feb 26, 2011 at 1:22 PM, Eric Firing wrote: > Dropping 2.6 any time soon would be too drastic for my liking, though. > It would require that any development work done on recent ubuntu > systems, for example, would require first installing a non-default > version of python.  So, I hope the

Re: [matplotlib-devel] git migration this weekend

On 02/26/2011 10:54 AM, Darren Dale wrote: > On Sat, Feb 26, 2011 at 3:52 PM, Darren Dale wrote: >> On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing wrote: >>> On 02/26/2011 09:26 AM, Darren Dale wrote: On Wed, Feb 16, 2011 at 2:19 PM, Eric Firingwrote: > On 02/16/2011 08:38 AM, Darren D

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 4:58 PM, Eric Firing wrote: > On 02/26/2011 10:54 AM, Darren Dale wrote: > > On Sat, Feb 26, 2011 at 3:52 PM, Darren Dale wrote: > >> On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing > wrote: > >>> On 02/26/2011 09:26 AM, Darren Dale wrote: > On Wed, Feb 16, 2011 at 2:1

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 5:58 PM, Eric Firing wrote: > On 02/26/2011 10:54 AM, Darren Dale wrote: >> On Sat, Feb 26, 2011 at 3:52 PM, Darren Dale  wrote: >>> On Sat, Feb 26, 2011 at 2:52 PM, Eric Firing  wrote: On 02/26/2011 09:26 AM, Darren Dale wrote: > On Wed, Feb 16, 2011 at 2:19 PM, E

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 6:15 PM, Benjamin Root wrote: > Github has been a wonderful tool for *developers*, but for > users of projects, I haven't seen the amount of sophistication and polish > that sourceforge has. > > I am personally fine with continuing to use sourceforge for the tracker (I > kn

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 3:24 PM, Darren Dale wrote: > > I agree that the github interface is not great. The github devs seem > to know that everybody complains about it. Yup. I hold on to the hope that, because it's so egregiously, painfully broken and braindead and it stands out so badly in com

Re: [matplotlib-devel] git migration this weekend

On 02/26/2011 01:44 PM, Fernando Perez wrote: > On Sat, Feb 26, 2011 at 3:24 PM, Darren Dale wrote: >> >> I agree that the github interface is not great. The github devs seem >> to know that everybody complains about it. > > Yup. I hold on to the hope that, because it's so egregiously, > painfull

Re: [matplotlib-devel] What's the status of the py3k branch?

--- On Sat, 2/26/11, Eric Firing wrote: > What about the non-interactive mode behavior--is it hard to > make the MaxOSX backend behave like the others in that > respect? I agree that this should be done, but I just haven't found the time to look at it (recently I have been looking at getting ani

Re: [matplotlib-devel] git migration this weekend

On Sat, Feb 26, 2011 at 6:14 PM, Eric Firing wrote: > It is impressive, and improves some aspects, but I don't see that it > makes the github tracker usable for new tickets.  I don't see any > facility for attaching a file--is this correct?  We really want users > with problems and suggestions to

Re: [matplotlib-devel] What's the status of the py3k branch?

On 02/26/2011 04:25 PM, Michiel de Hoon wrote: > --- On Sat, 2/26/11, Eric Firing wrote: >> What about the non-interactive mode behavior--is it hard to >> make the MaxOSX backend behave like the others in that >> respect? > I agree that this should be done, but I just haven't found the time to lo