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 ethan.furman
Recipients alex, barry, benjamin.peterson, docs@python, dstufft, eli.bendersky, ethan.furman, ezio.melotti, gvanrossum, isoschiz, ncoghlan, pconnell, python-dev, zach.ware
Date 2013-06-08.15:55:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370706942.8.0.57690941379.issue17947@psf.upfronthosting.co.za>
In-reply-to
Content
So, which is better?

To have a @unique class decorator as part of the module, or to have a UniqueEnum recipe in the docs?

A decorator is immediately usable, but requires remembering an extra line of code.

An example requires being put into a local utility module, but also serves as a guide to customising Enums.  (Took be about five tries to get it right. :/ )
History
Date User Action Args
2013-06-08 15:55:42ethan.furmansetrecipients: + ethan.furman, gvanrossum, barry, ncoghlan, benjamin.peterson, ezio.melotti, alex, eli.bendersky, docs@python, python-dev, zach.ware, pconnell, dstufft, isoschiz
2013-06-08 15:55:42ethan.furmansetmessageid: <1370706942.8.0.57690941379.issue17947@psf.upfronthosting.co.za>
2013-06-08 15:55:42ethan.furmanlinkissue17947 messages
2013-06-08 15:55:42ethan.furmancreate