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

Showing content from https://mail.python.org/pipermail/python-dev/2002-October/029628.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 ]

> Why break all modules when only one needs the old behavior?  Think
> about how from __future__ import is set up.

Because this is IMO a *very* small change, for which I don't want to
invoke such heavy guns.

--Guido van Rossum (home page: http://www.python.org/~guido/)

• 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