[stdlib-sig] Changing the 2.6 renames to not break pickle

[Brett Cannon]

On Mon, May 19, 2008 at 1:30 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> Le lundi 19 mai 2008 à 13:20 -0700, Brett Cannon a écrit :
>> On Mon, May 19, 2008 at 12:48 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
>> > Le lundi 19 mai 2008 à 12:21 -0700, Brett Cannon a écrit :
>> >> I think that gets __module__ set to the old module name even when code
>> >> is imported with the new name. It should also allow the Py3K warnings
>> >> to stick around without causing issues when importing from the new
>> >> name or suppressing other Py3K warnings. What do people think?
>> >
>> > Are 2.x pickles supposed to be re-usable under py3k?
>>
>> No. This is only so that 2.5 pickles work with 2.6.
>
> Ok. But still, it means that help(new_module_name) will display the old
> module name in the help contents?

Yep, nothing we can do about that without piling on even more support
infrastructure.

-Brett