I found pipenv works well. A package jrnl wouldn't run once built with pip but does run inside pipenv. This creates a virtual environment for building and running packages so once jrnl got built doing pipenv run jrnl runs the program. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Wed, 17 May 2023, Genes Lists wrote: > On 5/17/23 11:47, Martin Rys wrote: > > Some time ago, PEP 668[1] enabled distributions to mark the python > > installation as externally managed by a package manager, thus > > preventing pip from breaking the system by either installing packages > > to the system or locally in the home folder. > > > ... > > > > [1] https://peps.python.org/pep-0668/ > ... > > A good rationale - question on packaging for things that fall outside the > system repos. > > have several packages where in the install section of PKGBUILD it does > something like: > > pipopts="--isolated --ignore-installed --no-deps" > pip $pipopts install --root=$pkgdir dist/*.whl > > Will this continue to work or is there some change needed to accommodate this > change? > > I didn't see "--root" discussed in reference [1] > > thanks > > gene > >
