Hi Thomas, Besides figuring out where the repo url is, you have a second problem to solve:
The command `pip install -e some/path` already has something unpacked/checked-out in `some/path` to install in development mode. In which folder would the command `pip install -e some.project` unpack/checkout `some.project`? Cheers, Leo On 21 March 2017 at 05:13, Thomas Güttler <guettl...@thomas-guettler.de> wrote: > AFAIK it is impossible to do this: > > pip install -e foo > > You need to use the repo URL up to now: > > pip install -e git+https://example.com/repos/foo#egg=foo > > AFAIK the fast/short implementation of "pip install -e foo" does > not work, since pip can't access metadata of package foo without > downloading > the whole package. Or am I wrong - is this possible? > > But how cares for useless downloaded bytes? I don't care. > > It should be possible to download the whole package "foo", > then look at the metadata which is provided by it. Take > the canonical repo url, and then get the source from > the repo. > > AFAIK there is no official way to define a "Canonical Repo URL" up to now. > > If I want to provide it for my custom packages. How could I do this? > > Regards, > Thomas Güttler > > -- > Thomas Guettler http://www.thomas-guettler.de/ > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
