Gustavo Niemeyer wrote: > Also, is there any further work going on to improve the datetime module? > I'm not suggesting we should mirror mx.DateTime functionalities, but two > features I miss from mx.DateTime is the DateFrom(), which does its best > to parse a given string, and the RelativeDateTime() functionality. > > This has probably been raised in the past, so if that's the case, I'm > sorry. Marc-Andre, what's your opinion about reusing code from > mx.DateTime into datetime? The mxDateTime code comes under the eGenix Public License, so reuse is permittted under the terms of the license. That said, I doubt that you want to maintain a date/time parser in the Python core -- I certainly don't :-) > Anyway, reusing code or not, I'll probably put sometime on it in the > future, if this looks interesting to everyone (after I finish my current > python pendencies, like SRE's recursivity removal). -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, Sep 16 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
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