[Python-Dev] Module renaming and pickle mechanisms (original) (raw)
Lennart Regebro regebro at gmail.com
Mon May 19 18:00:43 CEST 2008
- Previous message: [Python-Dev] Module renaming and pickle mechanisms
- Next message: [Python-Dev] Module renaming and pickle mechanisms
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, May 19, 2008 at 2:08 PM, M.-A. Lemburg <mal at egenix.com> wrote:
Why can't we just provide a "from future import renamedmodules" which then provides all the new name to old name mappings in some form (e.g. module proxies or whatever) and leave the existing modules in 2.x untouched ?
If I understand this correctly, the pickles would then be compatible between 2.6 and 2.5, unless you did from future import renamed_modules, which would make the pickles compatible between 2.6 and 3.0. This sounds like the best solution to me, especially if the old names are still available after the future import, as all that would then be needed it to repickle all the pickles to convert from 2.5 to 3.0 pickles, right?
So, if I understood this correctly, that sounds like a perfect solution. :)
-- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64
- Previous message: [Python-Dev] Module renaming and pickle mechanisms
- Next message: [Python-Dev] Module renaming and pickle mechanisms
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]