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 eric.snow
Recipients Arfrever, daniel.urban, eric.snow, ezio.melotti, flox, jcea, ncoghlan
Date 2013-03-14.21:04:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Given that, it is probably also better to revert the namespace keyword
> to accepting an instance rather than a factory function, since the copy
> operation after execution of the class body is automatic.

Agreed.  Of course, the related note is rendered superfluous.  There is still the possibility of reusing the same namespace across successive class definitions, with the associated consequences.  However, since type.__new__() copies the namespace into a new dict, it mitigates the main concern: implicit modification to an existing class in the definition of another.
Date User Action Args
2013-03-14 21:04:13eric.snowsetrecipients: + eric.snow, jcea, ncoghlan, ezio.melotti, Arfrever, flox, daniel.urban
2013-03-14 21:04:13eric.snowsetmessageid: <>
2013-03-14 21:04:13eric.snowlinkissue17044 messages
2013-03-14 21:04:13eric.snowcreate