[Python-Dev] PEP 408 -- Standard library __preview__ package

Barry Warsaw barry at python.org
Sat Jan 28 02:48:10 CET 2012

On Jan 28, 2012, at 11:37 AM, Nick Coghlan wrote:

>Then the stdlib docs for that module (while it is in __preview__)
>would say "If you are able to easily use third party packages, package
><X> offers this API for multiple Python versions with stronger API
>stability guarantees. This preview version of the module is for use in
>environments that specifically target a single Python version and/or
>where the use of third party packages outside the standard library
>poses additional complications beyond simply downloading and
>installing the code."

Would it be acceptable then for a distro to disable __preview__ or empty it

The thinking goes like this: if you would normally use an __preview__ module
because you can't get approval to download some random package from PyPI, well
then your distro probably could or should provide it, so get it from them.  In
fact, if the number of __preview__ modules is kept low, *and* PyPI equivalents
were a requirement, then a distro vendor could just ensure those PyPI versions
are available as distro packages outside of the __preview__ stdlib namespace
(i.e. in their normal third-party namespace).  Then folks developing on that
platform could just use the distro package and ignore __preview__.

If that's acceptable, then maybe it should be explicitly so in the PEP.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120127/1171a43f/attachment.pgp>

More information about the Python-Dev mailing list