Message 249505 - Python tracker

➜

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	gvanrossum
Recipients	Guido.van.Rossum, Mark.Shannon, benjamin.peterson, eltoder, gvanrossum, larry, lemburg, njs, pitrou, rhettinger, serhiy.storchaka, vstinner
Date	2015-09-01.19:26:04
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
I don't think I told you to do it this way -- that message of mind sounded pretty noncommittal in all directions. I do understand your predicament. Can you live with just a special case for modules? __class__ assignment is full of non-portable special cases already. Given how close we are to the release we should tread with a lot of care here -- rolling back a diff is also a big liability. Maybe the "right" solution is to allow __dict__ assignment for modules. But we're too close to the release to add that. Perhaps we can revisit the right way to do it for 3.6?

I don't think I told you to do it this way -- that message of mind sounded pretty noncommittal in all directions.

I do understand your predicament. Can you live with just a special case for modules? __class__ assignment is full of non-portable special cases already.

Given how close we are to the release we should tread with a lot of care here -- rolling back a diff is also a big liability.

Maybe the "right" solution is to allow __dict__ assignment for modules. But we're too close to the release to add that. Perhaps we can revisit the right way to do it for 3.6?

History
Date	User	Action	Args
2015-09-01 19:26:05	gvanrossum	set	recipients: + gvanrossum, lemburg, rhettinger, pitrou, vstinner, larry, benjamin.peterson, njs, Mark.Shannon, eltoder, serhiy.storchaka, Guido.van.Rossum
2015-09-01 19:26:04	gvanrossum	set	messageid: <[email protected]>
2015-09-01 19:26:04	gvanrossum	link	issue24912 messages
2015-09-01 19:26:04	gvanrossum	create