[IPython-dev] [Fwd: Re: making pdoc, pdef, and pinfo more generally useful]

Fernando Perez Fernando.Perez at colorado.edu
Fri Oct 13 09:29:33 CDT 2006


Thanks for the suggestions.  Note that I'm forwarding this manually to the 
list since it discards non-subscriber posts (too much spam).

Cheers,

f

-------- Original Message --------
Subject:
Re: making pdoc, pdef, and pinfo more generally useful
From:
Stefan Reichör <stefan at xsteve.at>
Date:
Fri, 13 Oct 2006 11:13:28 +0200
To:
ipython-dev at scipy.net

"Ville M. Vainio" <vivainio at gmail.com> writes:

 > > On 10/12/06, R. Bernstein <rocky at panix.com> wrote:
 > >
 >> >> I didn't do this initially because, well, I'm currently backed up in
 >> >> patches, what I have works and I don't want to destroy that, and
 >> >> adding my own version control on top of SVN checked-out sources is a
 >> >> bit whacky.
 > >
 > > Not really all that whacky, esp. if the svn is for the "official,
 > > stable version" that is expected to work rather predictably. Too bad
 > > svn is not a distributed vcs...
 > >
 > > I recommend bzr (bazaar-ng) for your "own", on-top-of-svn version
 > > control, works really well with local versions of files and no need
 > > for repository administration.
 > >
 > > See http://doc.bazaar-vcs.org/bzr.dev/tutorial.htm if you are interested.

I also think that bzr is a good solution for that kind of stuff.
However, I use Mercurial Queues (mq) for tracking svn repositories and
generating patches.

Since R. Bernstein uses Emacs, let me do some advertisement for emacs dvc:
http://www.xsteve.at/prg/emacs_dvc/index.html

I have added emacs support for mq. That way I can easily build patches
for upstream projects.

If anyone would like to try this setup, feel free to ask  ;-)


Stefan.



More information about the IPython-dev mailing list