See https://github.com/pypa/pip/issues/7555 for details on this.
Stuart McGraw wrote:
“Hello,
First time trying to use Python's package tools and I'm attempting to use pip
to install from a local project:
python3 -m pip install --user --upgrade --no-deps ./
I have a simple directory structure
Hello,
First time trying to use Python's package tools and I'm attempting to use pip
to install from a local project:
python3 -m pip install --user --upgrade --no-deps ./
I have a simple directory structure very similar to that recommended in
https://packaging.python.org/tutorials/packaging
On Thu, Jun 25, 2020 at 12:37 AM Paul Moore wrote:
> I think the key message here is that you won't be *re*-inventing the
> wheel. This is a wheel that still needs to be invented.
It _was_ invented, but it is off round and gives a rough ride. As
noted in the first post this:
__requires__ = ['s
On Tue, 2020-06-23 at 15:51 -0700, David Mathog wrote:
> What I am after is some method of keeping exactly one copy of each
> package-version in the common area (ie, one might find foo-1.2,
> foo-1.7, and foo-2.3 there), while also presenting only the one
> version of each (let's say foo-1.7) to a
On Thu, 25 Jun 2020 at 00:06, David Mathog wrote:
>
> Thanks for the link. Unfortunately there was not a reference to a
> completed package that actually did this. As in, I really do not want
> to reinvent the wheel. Ugh, sorry, that's a pun in this context.
I think the key message here is that
