A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-February/116408.html below:

Provisional packages in the Python standard library

[Python-Dev] PEP 411: Provisional packages in the Python standard library [Python-Dev] PEP 411: Provisional packages in the Python standard libraryEric Snow ericsnowcurrently at gmail.com
Fri Feb 10 23:38:58 CET 2012
On Fri, Feb 10, 2012 at 1:13 PM, Jim J. Jewett <jimjjewett at gmail.com> wrote:
>
> Eli Bendersky wrote (in
> http://mail.python.org/pipermail/python-dev/2012-February/116393.html ):
>
>> A package will be marked provisional by including the
>> following paragraph as a note at the top of its
>> documentation page:
>
> I really would like some marker available from within Python
> itself.
>
> Use cases:
>
> (1)  During development, the documentation I normally read
> first is whatever results from import module; help(module),
> or possibly dir(module).
>
> (2)  At BigCorp, there were scheduled times to move as much
> as possible to the current (or current-1) version.
> Regardless of policy, full regression test suites don't
> generally exist.  If Python were viewed as part of the
> infrastructure (rather than as part of a specific
> application), or if I were responsible for maintaining an
> internal application built on python, that would be the time
> to upgrade python -- and I would want an easy way to figure
> out which applications and libraries I should concentrate on
> for testing.

+1 on both

-eric
More information about the Python-Dev mailing list

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