[Python-Dev] Policy Decisions, Judgment Calls, and Backwards Compatibility (was Re: splitext('.cshrc')) (original) (raw)
Steven H. Rogers steve at shrogers.com
Fri Mar 9 04:11:20 CET 2007
- Previous message: [Python-Dev] Policy Decisions, Judgment Calls, and Backwards Compatibility (was Re: splitext('.cshrc'))
- Next message: [Python-Dev] Policy Decisions, Judgment Calls, and Backwards Compatibility (was Re: splitext('.cshrc'))
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
glyph at divmod.com wrote:
In the past I've begged off of actually writing PEPs because I don't have the time, but if there is interest in codifying this I think I don't have the time not to write it. I'd prefer to document the pending/deprecate/remove policy first, but I can write up something more complicated about community buildbots and resolving disputes around potential breakages if there is actually no consensus about that.
Please do write this up. It's a good policy and should be codified.
Steve
- Previous message: [Python-Dev] Policy Decisions, Judgment Calls, and Backwards Compatibility (was Re: splitext('.cshrc'))
- Next message: [Python-Dev] Policy Decisions, Judgment Calls, and Backwards Compatibility (was Re: splitext('.cshrc'))
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]