[IPython-dev] IPython Patch

Fernando Perez fperez.net at gmail.com
Sat Aug 16 23:41:01 EDT 2008

Hi Laurent,

On Sat, Aug 16, 2008 at 3:28 AM, Laurent Dufréchou
<laurent.dufrechou at gmail.com> wrote:
> Hi cody,
> Wow, thanks a lot for this patch! This was something I didn't knew how to
> solve! Thks a lot.
>> I made the changes to the code on the editra-plugins svn. Hopefully its
>> not too out of date from the latest ipython.
> Yeah, ipython guys have undergone big change in the frontend handling, so
> I'm waiting the new code base to make the frontend evolve. That's why this
> portion of code has not evolved since then :)
> Ipython 0.9 (that is going to be commited soon) will have all the new code
> base and will be ready for testing new code.
> So I will port al my 'old' code to this new arch, soon.
> Stay tuned ;)

please put your code in a branch we can all see, by doing something like

cd your_working_branch
bzr push  --remember lp:~laurent-dufrechou/ipython/trunk-dev

This will give everyone access to the code you're working on for
review and merge.  Also please make sure that when you merge a change
sent in by an outside contributor, you list this fact in the commit
message and record it as a standalone change  as

bzr commit --author="Name of other contributor"

This way we can then, on each release, properly credit external users
who make contributions to the project, which is very important.

By the way, I've just done what I suggested above and pushed my local
copy of trunk here:


so others can review also whatever I'm doing at any time.  As I said
in my previous email I want to be the only one to handle merging for a
few days, but that's *only while we figure out the details*.  I think
a good way to use launchpad will be for everyone to do their work on a
visible branch like this (in addition to possibly shared branches
where several people are working on something together).  These
branches can be kept forever in 'merge pending' status, as we all go
about implementing things and merging into trunk.



More information about the IPython-dev mailing list