PEP 668 refers to this document as being the definitive one: Externally Managed Environments <https://packaging.python.org/en/latest/specifications/externally-managed-environments/#externally-managed-environments>. Reading it, I see that everything is optional and has to be set up by the distro's packaging people. Some of the these people may understand the ins and outs better than others, so the way these details are set up can be different between distros.
IOW, Linux business as usual. On Tuesday, July 30, 2024 at 9:17:57 AM UTC-4 lewis wrote: > On Monday, July 29, 2024 at 11:04:13 PM UTC+10 [email protected] wrote: > > I've been reluctant to install a WSL distro on my Windows 10 machine in > case something would go wrong and mess up Windows itself. Was it pretty > straightforward? > > > I didn't find the installation straightforward due to the problem with git > and pip install -r requirements.txt > However I persisted, my Windows system is not messed up, and Leo runs. > myLeoSettings.leo file works fine on wsl2 running Debian and Ubuntu. > > I found this statement confusing: > > > *If you wish to install a non-Debian packaged Python application, it > may be easiest to use pipx install xyz, which will manage a virtual > environment for you. Make sure you have pipx installed.* > > So you install pipx and use it to install leo. It creates venvs for you at > .local/pipx/venvs/leo/ > but pip does not recognise it. > > I would like to understand if PEP 668 affects all linux installs this way. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/3ba75488-f024-4ed3-b974-f8e3cb9b652en%40googlegroups.com.
