Hamish Lawson wrote: > One of the arguments put forward against renaming the existing time > module to _time (as part of incorporating a pure-Python strptime > function) is that it could break some builds. Therefore I'd suggest that > it could be a useful principle for any C extension added in the future > to the standard library to have an accompanying pure-Python wrapper that > would be the one that client code would usually import. Sounds like a plan :-) BTW, this reminds me of the old idea to move that standard lib into a package, eg. 'python'... from python import time. We should at least reserve such a name RSN so that we don't run into problems later on. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/ Meet us at EuroPython 2002: http://www.europython.org/
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