I think I may have a solution, pipx
<https://pipx.pypa.io/stable/docs/#pipx-install>:
$ sudo pip install pipx
Then you can do (no sudo):
$ pipx install -v duplicity==2.2.2 --suffix=222
$ pipx runpip duplicity222 install -r requirements.txt
$ duplicity222 -V
There are many more options, but this seems to be the "clean" way to go. Plus
pipx is supported by PyPA.
For me the question is how to convince the apt-only crowd to do it this way.
Wish they had left setup.py alone and just provided enhancements. I'd like to
get back to improving, not packaging.
...Ken
On Wed, Apr 3, 2024 at 1:17 PM Kenneth Loafman <kenneth@loafman.com
<mailto:kenneth@loafman.com>> wrote:
Hi ede,
It looks like the PyPA has gotten to you too!
The problems we're having with setup are numerous, especially since they've
gone to managed environments for Python. We are going to have to figure out
how to create a venv and install duplicity into that for setup.py to work
correctly. There are packages out there that do it, but using them is a PITA.
I'm still trying to find a tolerable tool. The install process changes every
day it seems.
I do not have a clear answer for your question, other than the PITA of
splattering venvs all over the place. It's like someone perverted Python
packaging to make snaps more acceptable.
One possible answer is to go back to a much older version of setup.py, one
without pyproject.toml, and use that to make the multiple versions you need.
You will also have to go back to older versions of packaging, setuptools,
wheel, etc.
PyPA has made a real mess of the install process. That's especially true
for users that refuse to use pip to update their modules.
...Thanks,
...Ken
On Wed, Apr 3, 2024 at 11:57 AM edgar.soldin--- via Duplicity-talk
<duplicity-talk@nongnu.org <mailto:duplicity-talk@nongnu.org>> wrote:
hey Ken,
for like always i could install duplicity versions in parallel
user-local like
PREFIX=~/_apps/duplicity-2.1.5
~/duplicity.venv/bin/python setup.py install --prefix="$PREFIX"
--install-lib="$PREFIX"
~/_apps/duplicity-2.1.5/bin/duplicity --version
this fails horribly now after the setuptools rework.
how, apart from creating a venv for each version, can i install
different duplicity versions in parallel for testing?
thanks.. ede
_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org <mailto:Duplicity-talk@nongnu.org>
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk>