#๐Ÿ”’ How to deal with annoying paths in (now required) virtual environments?

17 messages ยท Page 1 of 1 (latest)

sonic breach
#

pip in recent Linux now refuses to work

If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed.

what is a good way to avoid typing this annoyingly long qualified paths?
I though about ./bin/pip but that will break as soon as I am in some directory within
Having different path to python in every project is also really annoying.

At that point I am considering making one shared virtual environment for all my projects and making aliases, and working as I worked before.

copper marshBOT
#

@sonic breach

Python help channel opened

Remember to:

  • Ask your Python question, not if you can ask or if there's an expert who can help.
  • Show a code sample as text (rather than a screenshot) and the error message, if you've got one.
  • Explain what you expect to happen and what actually happens.

:warning: Do not pip install anything that isn't related to your question, especially if asked to over DMs.

normal coyote
#

generally people will use a packaging/environment manager (like poetry or uv) that handles this for them

sonic breach
normal coyote
sonic breach
#

Can you have uv-managed project and pip-managaed projects on the same system?

#

Or will they conflict with each other?

normal coyote
sonic breach
#

๐Ÿ Installs and manages Python versions.
and these will not conflict with system Python?

sonic breach
normal coyote
junior sparrow
opaque trout
#

I'd recommend using uv for everything.

copper marshBOT
#
Python help channel closed for inactivity

This help channel has been closed. Feel free to create a new post in #1035199133436354600. To maximize your chances of getting a response, check out this guide on asking good questions.