[IPython-dev] IPython module and package reorganization
Wed Jul 1 16:15:06 CDT 2009
On 2009-07-01 16:09, Ville M. Vainio wrote:
> On Wed, Jul 1, 2009 at 10:46 PM, Fernando Perez<email@example.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).
The Python developers have requested that projects *not* use the Python 3
transition as an opportunity to break compatibility.
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as though it had
an underlying truth."
-- Umberto Eco
More information about the IPython-dev