Doesn't install packages from source repository about pip-accel

[hvdklauw]

can confirm this.

However, I have never seen the use for the -e option for remote repositories, the only use really is if you have a subrepository which you want to install as source.

The above command could be changed to:

pip-accel install http://github.com/asavoy/django-mobile/archive/9dfae7664636de647bcfd71665b7bdf0c24a35d8.zip

It will do a normal python setup.py install instead of a python setup.py develop.

[asavoy]

Thanks, I wasn't aware that -e would do a different kind of install, to standard usage. (The long option form --editable is suggestive of that, yet somehow I missed it!)

And in light of this, I'd agree it's not as valuable a use case to support. I've switched to zip archive URLs without issue, under pip and pip-accel.

[mbrochh]

that would work for github, but does bitbucket offer a similar option as well?

[hvdklauw]

Yes, that also works:
https://bitbucket.org/hpk42/pytest/get/ef299e5.tar.bz2

[asavoy]

I eventually settled upon a different method, because PyCharm kept insisting on refetching the archive file:

pip-accel install git+https://github.com/asavoy/django-mobile.git@b6088e1c#egg=django-mobile

It's simply removing the -e option altogether -- pip and pip-accel both work fine when given a VCS location to install. This is indeed installing from a source repository (it should even work with private repos), so I think this issue should be considered invalid. Perhaps pip-accel could simply state it doesn't support the -e option and leave it at that.

[hvdklauw]

Nice, if that works it's great.

I think however the -e is still viable for some cases and it would be nice to support it.

[mbrochh]

Hmm somehow my comment from yesterday got lost: I think the problem simply is that pip-accel does not create the *.egg-info file in venv/lib/python2.7/site-packages which contains the path to venv/src/cloned-repo-name

[xolox]

In the beginning I blindly added support for pip install --editable but it really doesn't make sense at all, so I'm considering removing it. The point is that pip install --editable is like python setup.py develop IIUC; it just creates Python style symbolic links. If pip-accel caches a binary distribution created like this, the cached binary distribution will forever be tied to the location of the original files; if you remove them the cached binary distribution will also break. That was not how I envisioned pip-accel working; once a binary distribution is cached it should be independent from the state of the local system (except where not otherwise possible, i.e. binary dependencies). Does anyone have thoughts about this?

[fdv]

Having the same problem using pip-accel system-wide with a requirements file. For some reasons, I had it working for a few days, then ran into that issue. Not sure how to bypass it though.

[xolox]

I previously suggested I might simply remove support for editable packages, but that would make pip-accel less compatible with pip. What I've now done instead (in eccf0ba) is to add explicit support for editable packages. With this change editable packages bypass the binary cache and are installed using pip install --no-deps --editable $url (to avoid me having to reimplement the same logic pip already has). Can someone try this out and tell me if it resolves this issue? Thanks for the feedback everyone!

[xolox]

I believe the problems reported here have been resolved for quite a while now so I'm going to close this issue. If anyone is still having problems with this then feel free to reopen the issue or open a new one. Thanks for the feedback everyone!