Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Need a way to build entry points from existing software #480

cjw296 opened this Issue Mar 12, 2012 · 3 comments


None yet
5 participants

cjw296 commented Mar 12, 2012

So, I created a virtualenv with --system-site-packages as the python is question is EPD 7.2 which has ipython, numpy, etc all ready and compiled in.

I now want to run ipython using that virtualenv, but I have no way to create the entrypoint script other than by re-installing ipython, which kinda defeats the point of --system-site-packages ;-)

How about something like:

pip link ipython


pip install --system ipython

The latter actually feels better to me :-)


carljm commented Mar 12, 2012

I definitely think this feature makes sense, it's just a question of bikeshedding how we spell it :-) I'm not a big fan of reusing "install" as this is quite a different operation we're talking about. I'm almost tempted to spell it pip import, as we're sort of "importing" the existing system package into the virtualenv.

But whoever builds the bikeshed gets to paint it :-)


bernardofire commented Mar 12, 2012

Since the ipython is already installed in the system, pip install doesn't make sense.
I think pip import would be better too.


dstufft commented Mar 24, 2017

Closing this, I don't believe it to be a useful enough feature to warrant holding open a ticket or adding the mental overhead of a new command.

@dstufft dstufft closed this Mar 24, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment