On Thu, Mar 27, 2014 at 10:11 AM, Stephen J. Turnbull <stephen at xemacs.org> wrote: > Nick Coghlan writes: > > > On 27 Mar 2014 07:02, "Guido van Rossum" <guido at python.org> wrote: > >> Actually, the first step is publish it on PyPI, the second is to > >> get a fair number of happy users there. The bar for getting something > >> included into the stdlib is pretty high > > > The "why not a third party module?" bar also got a fair bit higher > > with Python 3.4 - by bundling pip, we have deliberately made third > > party modules easier to consume, thus weakening the convenience > > argument that applies to stdlib inclusion. > > Maybe. That depends on if you care about the convenience of folks who > have to get new modules past Corporate Security, but it's easier to > get an upgrade of the whole shebang. I don't think it's ever really > been resolved whether they're a "typical case that won't go away" or a > special group whose special needs should be considered. > > Steve And random pieces of C included in the standard library can be shuffled under the carpet under the disguise of upgrade or what are you suggesting?
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