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 demian.brecht
Recipients demian.brecht, ethan.furman, r.david.murray
Date 2016-02-18.19:22:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1455823334.67.0.448455523401.issue26380@psf.upfronthosting.co.za>
In-reply-to
Content
> I don't have a firm opinion at this point -- can you give a few examples of how this will help in code?

It'll help solely with consistency across projects. Generally, using constants are generally favored over using hardcoded values. Mainly, it helps reduce typos. Some projects use literals, others use project-specific constants. It's something that I've found myself redefining over various projects, and I just though "why couldn't this be added to the standard library, given it's an attribute of the HTTP/1.1 RFC"?

/Very/ minor, personal annoyance.

The updated patch fixes the OPTION typo.
History
Date User Action Args
2016-02-18 19:22:14demian.brechtsetrecipients: + demian.brecht, r.david.murray, ethan.furman
2016-02-18 19:22:14demian.brechtsetmessageid: <1455823334.67.0.448455523401.issue26380@psf.upfronthosting.co.za>
2016-02-18 19:22:14demian.brechtlinkissue26380 messages
2016-02-18 19:22:14demian.brechtcreate