On Tue, Mar 24, 2009 at 1:23 PM, Jess Austin <jaustin at post.harvard.edu> wrote: > On Tue, Mar 24, 2009 at 3:14 PM, Guido van Rossum <guido at python.org> wrote: >> Please don't do this. We need stable APIs. Trying to switch the entire >> community to use CapWord APIs for something as commonly used as >> datetime sounds like wasting a lot of cycles with no reason except the >> mythical "PEP 8 conformance". As I said, it's a pity we didn't change >> this at the 3.0 point, but I think going forward we should try to be >> more committed to slow change. Additions of new functionality are of >> course fine. But renamings (even if the old names remain available) >> are just noise. > > OK, I had misunderstood your earlier message. Sorry for the confusion. No problem! I was probably using shorthand that only experienced devs understood. I hope you'll find other things to contribute! -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4