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 r.david.murray
Recipients ezyang, federico.reghenzani, r.david.murray
Date 2012-03-27.12:33:12
SpamBayes Score 6.504062e-05
Marked as misclassified No
Message-id <1332851593.45.0.0206464818995.issue14416@psf.upfronthosting.co.za>
In-reply-to
Content
That's probably reasonable (we have precedents for that in other modules), except that that's not how the older possibly-not-there constants work.  For backward compatibility reasons we can't change the older constants, but I don't see any reason we can't do it for the "new" ones.

We can fix the omission of SYSLOG in the 2.7 and 3.2 docs.  That should be a separate patch.
History
Date User Action Args
2012-03-27 12:33:13r.david.murraysetrecipients: + r.david.murray, ezyang, federico.reghenzani
2012-03-27 12:33:13r.david.murraysetmessageid: <1332851593.45.0.0206464818995.issue14416@psf.upfronthosting.co.za>
2012-03-27 12:33:12r.david.murraylinkissue14416 messages
2012-03-27 12:33:12r.david.murraycreate