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 ncoghlan
Recipients ethan.furman, larry, ncoghlan, python-dev, rhettinger, serhiy.storchaka, xiang.zhang, yselivanov
Date 2017-01-24.06:26:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7crRophAFxwX6yhMw6g5_rgZ=0X1STpWpuE-Q6AdXBPTg@mail.gmail.com>
In-reply-to <CADiSq7c1gf-DYy9gE_xHmpzTWQVMxzWCY8pxUh=2wRJn8dey_Q@mail.gmail.com>
Content
Enum's interaction with the help subsystem has always been somewhat
fragile: http://bugs.python.org/issue18693

In this case, I think a reasonable quick fix would be to add the new text
to the expected output for enum instances (allowing this issue to be closed
again), and then file a separate issue about offering a way to omit that
text for types that discourage or don't allow dynamic creation of new
instances.
History
Date User Action Args
2017-01-24 06:26:51ncoghlansetrecipients: + ncoghlan, rhettinger, larry, ethan.furman, python-dev, serhiy.storchaka, yselivanov, xiang.zhang
2017-01-24 06:26:51ncoghlanlinkissue29338 messages
2017-01-24 06:26:50ncoghlancreate