[Python-ideas] stdlib upgrades

Lie Ryan lie.1296 at gmail.com
Mon Jun 7 12:23:13 CEST 2010

On 06/07/10 16:33, Ron Adam wrote:
> On 06/01/2010 08:22 PM, Brett Cannon wrote:
>> I can only see two scenarios that might be considered acceptable to
>> address these issues.
>> One is that when new modules are accepted into the stdlib they are
>> flagged with a ExpermintalWarning so that people know that no
>> backwards-compatibility promises have been made yet. That gets the
>> module more exposure and gets python-dev real-world feedback to fix
>> issues before the module calcifies into a strong
>> backwards-compatibility. With that experience more proper decisions
>> can be made as to how to change things (e.g. the logging module's
>> default timestamp including microseconds which strptime cannot parse).
> Would it be possible to have a future_lib that gets enabled with
> something like...
>    from __future__ import future_lib
> These *new* library modules and packages won't be visible by default.
> Maybe they stay there until the next major version or possible some set
> period of time.

reading that gives me a chuckle. Perhaps that would be a vote to change
the name 'future'.

More information about the Python-ideas mailing list