[IPython-user] Bug in ipython -pylab and %who ?

[Fernando Perez]

On Sun, Mar 9, 2008 at 11:44 AM, Ville M. Vainio <vivainio@gmail.com> wrote:

>  Launchpad now has the svn imported, so the history is not "lost" -
>  it's still available there, albeit in different branch. It doesn't
>  really matter, since there won't be branching from that old stuff.
>  That is, we can do "bzr annotate" on that old branch to find out why
>  some commit is there, but we don't need that history for branch/merge
>  tracking.

Good, thanks.  Is there a way to see that history with a browser, like
Trac shows it for SVN?  I sometimes find it handy with Trac, which is
why I want to make sure we have it easily accessible.

>  The fact that we now don't have the entire history in the branch is a
>  win for performance (especially bzr push) and size as well, due to the
>  fact that bzr branches will contain the full history (even if shared
>  repos help a little bit here - but launchpad does not implement shared
>  repos yet). Also, there is a symlink in SVN, which breaks bzr for
>  Windows (for now at least). That means the fresh, clean bzr repository
>  is best.

That's OK, I don't think most users need it for day to day use, I just
want  to make sure it's available somewhere in case we need it.

>  >  It seems that  upstreaming back into SVN for now is the easiest
>  >  solution, or do you have a different plan?
>
>  I won't do this "regularly", but I will probably just dump everything
>  to svn before we release in one commit (for convenience of people who
>  follow the svn). I don't think we should do the release from svn,
>  though, and the bzr stable-dev branch will have the "authoritative"
>  stuff. That really means svn is a second-class citizen now.

That  sounds fine.  In that case though, it would be good if you could
update the instructions on the site so users who like to keep up with
the development branches can continue to follow.

Cheers

f