determine why appackager doesn't work with pipenv 2023.12.1

[freddrake]

Setting editable to false in the lock file doesn't seem to have any effect. Investigation needed.

[freddrake]

The most recent "good" version of pipenv is version 2023.7.23; the problem is introduced in version 2023.8.19.

This is a known issue in pipenv: pypa/pipenv#6054

One approach to working around this is to examine the constructed venv to identify any editable installs, remove them, and re-install using the pip from the venv without the editable flag.

[wyllys66]

Im currently using version 2023.10.24. However, I'm also not using appackager at the moment, but this is good info to have.

[freddrake]

Im currently using version 2023.10.24. However, I'm also not using appackager at the moment, but this is good info to have.

If you're only using pipenv to build locally so you'll be using a copy of your application sources anyway, there's not a problem. It's only when you're using an appackager-constructed .deb that you care about this (or any other tool that expects non-editable installs).

[freddrake]

This issue also describes the problem: pypa/pipenv#6221

Just got bitten by this again; appackager should check the pipenv version against known-bad versions and report the incompatibility to the user.

[wyllys66]

Thanks for the update. This hasn't bitten me lately, but I'll keep an eye on it.