This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients brett.cannon, eric.snow, ncoghlan
Date 2016-01-16.18:14:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I totally agree proper notes in the What's New doc need to be in place to explain that people need to update.

How about I tweak the __package__ change to continue to prefer __package__ over __spec__.parent, but raise an ImportWarning when they differ? It can also fall back to __spec__.parent if __package__ isn't defined and simply not worry about the lack of __package__? Then we can do an ImportWarning for all of the other attributes when we discover a difference so people have time to migrate to updating both locations, and then eventually we can invert the priority and then after that drop the module attributes.
Date User Action Args
2016-01-16 18:14:14brett.cannonsetrecipients: + brett.cannon, ncoghlan, eric.snow
2016-01-16 18:14:14brett.cannonsetmessageid: <>
2016-01-16 18:14:14brett.cannonlinkissue21762 messages
2016-01-16 18:14:14brett.cannoncreate