A library in PyPi  still requires installing it, which undermine many of the benefits. It won't help me with my gist/activestate recipe, code that I send to a friend, etc. I want to lower the barrier of inexperienced users.

As a documentation of dependencies it will suffice indeed.


On Mon, Sep 19, 2016 at 7:38 PM Ethan Furman <ethan@stoneleaf.us> wrote:
On 09/19/2016 09:25 AM, אלעזר wrote:

> Many proposals to add something to stdlib are rejected here with the suggestion to add such library to pypi first. As noted by someone, pypi is not as reachable as stdlib, and one should install that package first, which many people don't know how. Additionally, there is no natural distinction between 3rd party dependencies and in-project imports (at least in tiny projects).
> This can be made easier if the first line of the program will declare the required library, and executing it will try to download and install that library if it is not installed yet. Additionally, the 3rd party dependencies will be more explicit, and editors can then allow you to search for them as you type.
> Of course it is *not* an alternative for real dependency management, but it will ease the burden on small scripts and tiny projects - which today simply break with errors that many users does not understand, instead of simply asking permission to install the dependency.

This should start out as a library on PyPI.  (Sorry, couldn't resist. ;)

Actually, it should.  Perhaps a name of "import_pip" would make sense?  Any hurdles faced by this library would be (mostly) the same as a stdlib version.

Python-ideas mailing list
Code of Conduct: http://python.org/psf/codeofconduct/