Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2002-October/029606.html below:

[Python-Dev] float atime/mtime/ctime - a bad idea?

• Previous message: [Python-Dev] float atime/mtime/ctime - a bad idea?
• Next message: [Python-Dev] float atime/mtime/ctime - a bad idea?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Martin v. L=F6wis wrote:
> "M.-A. Lemburg" <mal@lemburg.com> writes:
>=20
>=20
>>If you're suggesting a new API, why not have it return one of
>>the new datetime objects ?
>=20
>=20
> Wouldn't that require to implement this type first?

AFAIK, PythonLabs is working on this. Even though development
seems to have stalled recently...

See CVS:/python/nondist/sandbox/datetime/

--=20
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
_______________________________________________________________________
eGenix.com -- Makers of the Python mx Extensions: mxDateTime,mxODBC,...
Python Consulting:                               http://www.egenix.com/
Python Software:                    http://www.egenix.com/files/python/

• Previous message: [Python-Dev] float atime/mtime/ctime - a bad idea?
• Next message: [Python-Dev] float atime/mtime/ctime - a bad idea?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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