[IPython-dev] IPython module and package reorganization

Ville M. Vainio vivainio at gmail.com
Wed Jul 1 17:09:49 EDT 2009

On Wed, Jul 1, 2009 at 10:46 PM, Fernando Perez<fperez.net at gmail.com> wrote:

> One aspect of this change does worry me though: there's a LOT of code
> in the wild that embeds ipython in all manner of tools, and we'd be
> breaking all of that with this change.  While we're all on board with
> doing backwards-incompatible changes, it would be nice to keep *some*
> level of backwards compatibility, even if done with shim layers.  We
> could provide a few shims so embedding code like

One more thought - perhaps this could be done after ipython works on
python 3? Then, the 2.x codebase could be left as-is, and the code in
py3 would be too (in the initial phase). But after a while, some
refactorings for the py3 version could start trickling in. This way,
2.x would be the "same old" python, whereas the py3 branch can
tolerate quite a bit of heavier breakage (because people are not
relying on its apis yet).

python 3 is a rather important project for ipython, since the
interactive prompt is where the users will be testing the py3 waters
first (and are probably less worried about having to jump a few hoops
to cater for IPython).

Ville M. Vainio

More information about the IPython-dev mailing list