"Eric S. Raymond" wrote: > > M.-A. Lemburg <mal@lemburg.com>: > > +1 all the way -- though these days I tend not to use the > > time module anymore. mxDateTime already does everything I want > > and there date/time values are objects rather than Python integers > > or tuples... ok, I'm just showing opff a little :) > > mxDateTime is on my short list of "why isn't this in the Python library > already?" Has it ever been discussed? Yes. I'd rather keep it separate from the standard dist for various reasons. One of these reasons is that I will be moving the mx tools into a new packaging scheme built on distutils -- installing it should then boil down to a simple RPM install or maybe a "python setup.py install" thanks to distutils. The package will then become a subpackage of the mx package. BTW, I see distutils as strong argument for *not* including more exotic packages in Python's stdlib. If this catches on, I expect that together with the Vaults we are not far away from having our own CPAN style archive of add-on packages. I also expect the commercial vendors like ActiveState et al. to take care of wrapping SUMO distributions of Python and the existing add-ons. -- Marc-Andre Lemburg ______________________________________________________________________ Company: http://www.egenix.com/ Consulting: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
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