[Python-Dev] Best practices for Enum (original) (raw)
Barry Warsaw barry at python.org
Mon May 13 16:19:38 CEST 2013
- Previous message: [Python-Dev] Best practices for Enum
- Next message: [Python-Dev] Best practices for Enum
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On May 12, 2013, at 04:49 PM, Raymond Hettinger wrote:
After the long design effort for the enum module, I'm sure there will be a forthcoming effort to apply them pervasively throughout the standard library.
We usually, explicitly, try not to do such wholesale adoptions in the stdlib when new features land. This is almost always a good idea in order to gain more experience with the new feature, reduce code churn (and thus the introduction of bugs), and aid in back/forward porting.
It seems entirely reasonable to me to be just as conservative about adoption of enums in the stdlib.
As Eli mentions, making the socket constants enums seems like a good test case.
-Barry
- Previous message: [Python-Dev] Best practices for Enum
- Next message: [Python-Dev] Best practices for Enum
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]