[issue21738] Enum docs claim replacing __new__ is not possible

Changes by Ethan Furman : -- assignee: ethan.furman -> docs@python nosy: +docs@python resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue21738] Enum docs claim replacing __new__ is not possible

Roundup Robot added the comment: New changeset 28c21f09719e by Ethan Furman in branch '3.4': Issue21738: clarify usage of __new__ in Enum subclasses https://hg.python.org/cpython/rev/28c21f09719e New changeset 91ec34801232 by Ethan Furman in branch 'default': Issue21738: clarify usage of __new__

[issue21738] Enum docs claim replacing __new__ is not possible

Ethan Furman added the comment: Common, no. And if the docs were silent on the matter that would be okay, but unfortunately the docs declare that it is not possible, which is just plain wrong. Patch also mentions _value_ as that is the supported interface when customizing __new__ methods. -

[issue21738] Enum docs claim replacing __new__ is not possible

Ezio Melotti added the comment: Is this common enough that it deserves to be documented? -- components: +Documentation nosy: +ezio.melotti type: -> enhancement ___ Python tracker __

[issue21738] Enum docs claim replacing __new__ is not possible

New submission from Ethan Furman: Replacing __new__ in an Enum subclass is not possible /in the subclass definition/, but is easily replaced via monkey-patching after the class has been defined. Docs need to be updated to reflect this. -- assignee: ethan.furman messages: 220372 nosy: