Message249505
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? |
|
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: <1441135564.95.0.388595960559.issue24912@psf.upfronthosting.co.za> |
2015-09-01 19:26:04 | gvanrossum | link | issue24912 messages |
2015-09-01 19:26:04 | gvanrossum | create | |
|