July 24, 2011
5:33 p.m.
On Sun, Jul 24, 2011 at 3:47 PM, Nick Coghlan <ncoghlan@gmail.com> wrote:
We've actually been down the 'namespace object' road years ago (Steve Bethard even wrote a proto-PEP IIRC) and it suffered the same fate as most enum PEPs: everyone has slightly different ideas on what should be supported, so you end up being faced with one of two options: 1. Ignore some of the use cases (so some users still have to do their own thing) 2. Support all of the use cases by increasing the API complexity (so many users will still do their own thing instead of learning the new API)
For enums, I think we should just pick a solution. I'm in favor of Barry Warsaw's version, flufl.enum. -- --Guido van Rossum (python.org/~guido)