The easiest way to check-out matplotlib source

(Answering only on the devel list.)

G�khan SEVER <gokhansever@...149...> writes:

How do you add you automatically check-out new added files from matplotlib
trunk? Is there a specific svn command for this?

Yes: svn update

$ python setupegg.py develop

That works with matplotlib as well. When you run svn update, if the
output shows that only Python files have been updated, you are all set
up. If C files have changed, you need to run the setupegg develop
command again to compile them.

···

--
Jouni K. Sepp�nen
http://www.iki.fi/jks

I am glad to see that setupegg.py develop works for matplotlib, too. (I
tested and worked well in my first try :slight_smile: Documentation building always
take longer time.

One more question: After svn co completes checking out the main trunk it says:

Checked out revision 7203.

However when I do:

In [1]: matplotlib.revision

Out[1]: ‘$Revision: 6887 $’

Which one is correct?

I am not going to ask much about git since it’s very experimental stage :slight_smile:

Thanks for the explanations…

Gökhan

···

On Mon, Jun 8, 2009 at 2:25 PM, Jouni K. Seppänen <jks@…278…> wrote:

(Answering only on the devel list.)

Gökhan SEVER <gokhansever@…149…> writes:

How do you add you automatically check-out new added files from matplotlib

trunk? Is there a specific svn command for this?

Yes: svn update

$ python setupegg.py develop

That works with matplotlib as well. When you run svn update, if the

output shows that only Python files have been updated, you are all set

up. If C files have changed, you need to run the setupegg develop

command again to compile them.

Jouni K. Seppänen

http://www.iki.fi/jks


Crystal Reports - New Free Runtime and 30 Day Trial

Check out the new simplified licensing option that enables unlimited

royalty-free distribution of the report engine for externally facing

server and web deployment.

http://p.sf.net/sfu/businessobjects


Matplotlib-devel mailing list

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Gökhan SEVER wrote:

One more question: After svn co completes checking out the main trunk it says:

Checked out revision 7203.

However when I do:

In [1]: matplotlib.__revision__
Out[1]: '$Revision: 6887 $'

Which one is correct?

The __revision__ in from matplotlib is the revision number on matplotlib's __init__.py file, which will always lag behind the revision of the most recently-changed file in the source tree (which is what SVN tells you).

Mike

···

--
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA