Re: [Duplicity-talk] installing different versions locally

[Kenneth Loafman]

Hi ede,

Welcome to my life!

I don't recall having pip install requirement for us.  I know with pipx you have to install them separately.  The README agrees with you.  Very confusing.

All I know is that when Ub24 hits there are going to be a lot of issues.  venvs will be mandatory to install duplicity, except the ancient duplicity of choice for the repo.

pipx works back to Ub20 for current duplicities.

pip is only working on Ub22 and above for the current version.

If you are on an older system you need to update pip, setuptools, and wheel to install newer duplicities.  Not from the repo, but from 'sudo pip install -U ...'.

It appears that we hit a boundary in 2022 where the new packaging is needed and the packaging in older versions matches older packaging.

Going forward with backwards packaging for older, repo-only, systems is very problematic.  It's all a matrix of which packaging version you have and which duplicity.  In your case you may need to install older packaging to get older duplicities to install.  Gets confusing in a hurry.

...Thanks,

...Ken

On Sun, Apr 7, 2024 at 10:18 AM <edgar.soldin@web.de> wrote:

going forward with it. i'm doing

python -m venv duplicity-2.2.3.venv
. duplicity-2.2.3.venv/bin/activate
pip install duplicity
duplicity --version

now it's missing fasteners? why are those dependencies not installed automagically on `pip install duplicity`? any idea?

regards.. ede


On 07.04.2024 17:04, edgar.soldin@web.de wrote:
> hey Ken,
>
> please correct me. but trying it out `pipx` it merely creates new venvs under `~/.local/share/pipx/venvs/`. then it installs dependencies in there doubling used file space as if i would have created a second venv manually myself. in conclusion it merely seems to save me from typing some but in turn takes over some control over these "application specific" venvs.
>
> ok, will do venv per version for now, for convenience, but am sure there is an easier, more space/time consuming way to realize this.
>
> sunny regards ..ede
>
> On 04.04.2024 18:06, Kenneth Loafman wrote:
>> 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>
>>