Re: [matplotlib-devel] Bleeding edge repository location

2011-04-12 Thread misayre
Have a look at https://github.com/matplotlib/matplotlib Cheers, Tobi Am 13.04.2011 00:03, schrieb Ian Bell: Where is the bleeding edge MPL source located? It doesn't seem to be subversion, http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/ stuck at revision 8988 or ht

Re: [matplotlib-devel] Bleeding edge repository location

2011-04-12 Thread Fernando Perez
On Tue, Apr 12, 2011 at 4:13 PM, John Hunter wrote: > Yes, I'll get thus fixed ASAP John, quick note: our local network is down (firewall transfer went awry), so if you need to rebuild the docs, you'll need to do it on another system than my box (I'm using a laptop over wireless to send this).

Re: [matplotlib-devel] Bleeding edge repository location

2011-04-12 Thread John Hunter
On Apr 12, 2011, at 6:03 PM, Ian Bell wrote: > Fernando, > > Perfect! Thanks for the information. Perhaps this can get updated on the > web somehow? Yes, I'll get thus fixed ASAP > > Ian > > > Ian Bell > Graduate Research Assistant > Herrick Labs > Purdue University > email: ib

Re: [matplotlib-devel] Bleeding edge repository location

2011-04-12 Thread Ian Bell
Fernando, Perfect! Thanks for the information. Perhaps this can get updated on the web somehow? Ian Ian Bell Graduate Research Assistant Herrick Labs Purdue University email: ib...@purdue.edu cell: (607)227-7626 On Tue, Apr 12, 2011 at 6:28 PM, Fernando Perez wrote: > Hi Ian, > > On Tu

Re: [matplotlib-devel] Bleeding edge repository location

2011-04-12 Thread Fernando Perez
Hi Ian, On Tue, Apr 12, 2011 at 3:03 PM, Ian Bell wrote: > Where is the bleeding edge MPL source located?  It doesn't seem to be > subversion, > http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/ > stuck at revision 8988  or https://github.com/astraw/matplotlib, which is >

[matplotlib-devel] Bleeding edge repository location

2011-04-12 Thread Ian Bell
Where is the bleeding edge MPL source located? It doesn't seem to be subversion, http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/stuck at revision 8988 or https://github.com/astraw/matplotlib, which is also from november of last year. If the bleeding-edge code is somewhe

Re: [matplotlib-devel] v1.0.x branch?

2011-04-12 Thread Fernando Perez
On Tue, Apr 12, 2011 at 8:55 AM, Darren Dale wrote: > That looks right to me. I find it easier to keep a local copy of > integration branches like v1.0.x and master BTW, I do that for my old stable branches: in addition to my main ipython repo directory, I keep a branches/ dir with static copies

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-12 Thread Fernando Perez
On Mon, Apr 11, 2011 at 2:19 PM, Darren Dale wrote: > > Brilliant, whatever they use allows uploading attachments. I know this isn't ideal, but a workaround for screenshots/images in mpl bug reports would be to upload them to something like imgur (free - no registration required): http://imgur.c

Re: [matplotlib-devel] v1.0.x branch?

2011-04-12 Thread Darren Dale
On Tue, Apr 12, 2011 at 9:38 AM, Michael Droettboom wrote: > Ok.  I hope I fixed it.  Here's what I did (from my clone of the > matplotlib/matplotlib repository) > >  > git branch v1.0.x e5970f4 >  > git push origin v1.0.x > > Looking at the commit history and contents at the tip of this branch, >

Re: [matplotlib-devel] v1.0.x branch?

2011-04-12 Thread Michael Droettboom
Ok. I hope I fixed it. Here's what I did (from my clone of the matplotlib/matplotlib repository) > git branch v1.0.x e5970f4 > git push origin v1.0.x Looking at the commit history and contents at the tip of this branch, everything looks ok. Someone want to verify for me? Mike On 04/12/20

Re: [matplotlib-devel] Cleanup tasks: Version checks

2011-04-12 Thread Michael Droettboom
On 04/12/2011 08:34 AM, Tobias Hoppe wrote: > I've read the status page for py3k and stumbled upon the cleanup tasks, > especially the version checks. I agree that calling sys.version_info[0] is > not a > smart choice. > > Why not use a new variable in __init__.py, something like a boolean > __is

Re: [matplotlib-devel] v1.0.x branch?

2011-04-12 Thread Michael Droettboom
Looking at the network, this seems to be the last commit on the 1.0.x branch: https://github.com/matplotlib/matplotlib/commit/e5970f4fa6589089ce60dad955831c7632606ead This seems to be where I somehow killed the 1.0.x branch by doing what I thought was a regular merge into master: https://githu

Re: [matplotlib-devel] v1.0.x branch?

2011-04-12 Thread Darren Dale
On Tue, Apr 12, 2011 at 9:47 AM, Jae-Joon Lee wrote: > Hi all, > > I thought we have a "v1.0.x" branch on the github repo, but no more. > > https://github.com/matplotlib/matplotlib/branches > > Hmm... > Is it (accidentally?) removed or do we now use another branch for > maintenance (although I don

[matplotlib-devel] v1.0.x branch?

2011-04-12 Thread Jae-Joon Lee
Hi all, I thought we have a "v1.0.x" branch on the github repo, but no more. https://github.com/matplotlib/matplotlib/branches Hmm... Is it (accidentally?) removed or do we now use another branch for maintenance (although I don't see any alternative)? Regards, -JJ

[matplotlib-devel] Cleanup tasks: Version checks

2011-04-12 Thread Tobias Hoppe
I've read the status page for py3k and stumbled upon the cleanup tasks, especially the version checks. I agree that calling sys.version_info[0] is not a smart choice. Why not use a new variable in __init__.py, something like a boolean __is_py3k__. Every module which needs a choice between py2