Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Python: Dev
Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives
 

Index | Next | Previous | View Flat


shazow at gmail

Mar 12, 2012, 7:23 PM


Views: 397
Permalink
Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives

Hi Pythonistas,

I've had the pleasure of speaking with Guido at PyCon and it became evident
that some of Python's included batteries are significantly lagging behind
the rapidly-evolving defacto standards of the community—specifically in
cases like urllib and urllib2, which lack important features provided by
alternatives like httplib2, requests, and my own urllib3.


Part 1:
I propose we add a snippet to the top of the documentation of specific
archaic standard modules which encourages users to investigate third-party
alternatives if they find the standard module frustrating or otherwise
lacking. These notes would target new users, including those coming from
other languages where the third-party library choices are not nearly as
amazing as they are in Python.

(For what it's worth, Guido has verbally agreed to a proposal of this
nature.)

What such a snippet might look like:

"Batteries are included with Python but sometimes they are old and
leaky—this is one of those cases. Please have a look in PyPI for more
modern alternatives provided by the Python community."

Additionally, I would like for us as a community to identify which other
standard libraries (cgi? ssl? others?) are candidates for this kind of
messaging in the official Python documentation.


Part 2:
I propose we add a new category of package identifiers such as "Topic ::
Standard Library Alternative :: {stdlib_package_name}" which authors of
libraries can tag themselves under. The documentation warning snippet will
provide a link to the appropriate PyPI query to list packages claiming to
be alternatives to the stdlib package in question.


Objections? Concerns? Improvements? What is the next step to making this
happen?

Pythonically yours,
- Andrey (on behalf of Ori Livneh, Kenneth Reitz, Brandon Rhodes, David
Wolever, and everyone else who contributed to this letter during our PyCon
sprint.)



P.S. Appendix: Here are some additional snippet alternatives that were
proposed:

> Batteries are included with Python but sometimes they are old and
leaky—this is one of those cases. Please have a look in PyPI for more
modern alternatives provided by the Python community.

> While this module has served Python programmers faithfully for many
years, there are now many powerful alternatives available as third-party
modules. To learn more about them, view the Python Package Index results
for the category "Topic :: Standard Library Alternative :: asyncore." —
[With the topic name as a hyperlink]

> This module has been identified by the community as crusty, a signal that
better alternatives exist outside the standard library. Because the Python
standard library is constained to maintain backward-compatibility, it does
not always reflect what is current or common in the Python community. If
you are not constrained to support legacy code, you may wish to browse the
Python Package Index for alternatives to this module.

Subject User Time
Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives shazow at gmail Mar 12, 2012, 7:23 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives rdmurray at bitdance Mar 12, 2012, 8:07 PM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives eliben at gmail Mar 12, 2012, 8:22 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives brian at python Mar 12, 2012, 8:58 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives shazow at gmail Mar 12, 2012, 9:14 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives tjreedy at udel Mar 12, 2012, 9:22 PM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives guido at python Mar 12, 2012, 9:40 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives brian at python Mar 12, 2012, 9:23 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives guido at python Mar 12, 2012, 9:43 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives eliben at gmail Mar 12, 2012, 9:48 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives anacrolix at gmail Mar 12, 2012, 10:10 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives senthil at uthcode Mar 12, 2012, 10:10 PM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives shazow at gmail Mar 12, 2012, 10:48 PM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives guido at python Mar 13, 2012, 7:52 AM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives senthil at uthcode Mar 12, 2012, 11:12 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives donald.stufft at gmail Mar 13, 2012, 6:34 AM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives p.f.moore at gmail Mar 13, 2012, 7:52 AM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives v+python at g Mar 13, 2012, 11:58 AM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives me at kennethreitz Mar 13, 2012, 12:13 PM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives brian at python Mar 13, 2012, 12:38 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives tjreedy at udel Mar 13, 2012, 12:49 PM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives guido at python Mar 13, 2012, 2:16 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives thomas at python Mar 13, 2012, 12:50 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives solipsis at pitrou Mar 13, 2012, 2:21 PM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives guido at python Mar 13, 2012, 2:38 PM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives anacrolix at gmail Mar 13, 2012, 8:31 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives steve at pearwood Mar 13, 2012, 4:55 PM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives solipsis at pitrou Mar 14, 2012, 2:07 AM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives eliben at gmail Mar 13, 2012, 9:03 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives anacrolix at gmail Mar 13, 2012, 10:49 PM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives solipsis at pitrou Mar 14, 2012, 2:39 AM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives stefan at bytereef Mar 14, 2012, 2:58 AM
            Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives solipsis at pitrou Mar 14, 2012, 3:00 AM
                Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives stefan at bytereef Mar 14, 2012, 3:20 AM
            Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives mark at hotpy Mar 14, 2012, 3:05 AM
                Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives rdmurray at bitdance Mar 14, 2012, 9:00 AM
                Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives tjreedy at udel Mar 14, 2012, 9:47 AM
        Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives anacrolix at gmail Mar 14, 2012, 9:26 AM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives julien at tayon Mar 14, 2012, 9:16 AM
    Re: Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives solipsis at pitrou Mar 14, 2012, 9:40 AM
    Docs of weak stdlib modules should encourage exploration of 3rd-party alternatives jimjjewett at gmail Mar 19, 2012, 12:12 PM

  Index | Next | Previous | View Flat
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.