@xssfox Hmm, is that singular venv allowed to contain pipx/uvx or equivalent?

[ancoghlan@mastodon.social]

@xssfox Hmm, is that singular venv allowed to contain pipx/uvx or equivalent?

[firesphere@cloudisland.nz]

@xssfox I'm speechless, why had I never thought of that!
Saves so much diskspace!

[nafithebear@snaggletooth.life]

@xssfox nooooo! XD

[faoluin@chitter.xyz]

@xssfox What if I program my python only against my system dependencies though uwu

[ams@infosec.exchange]

@xssfox ...venv does a worse job of handling deps and multiple python versions than portage.

[ellie@ellieayla.net]

@xssfox can the singular venv be built with a python from brew, so brew can just yank the python binary & stdlib the symlinks point to? That would be an exciting day.

[xssfox@cloudisland.nz]

I've been informed you can also just use someone else's venv

[Guest]

@xssfox they need to have the same absolute paths as you though

[daisy@cloudisland.nz]

@xssfox venvs as a service

[xssfox@cloudisland.nz]

@daisy pypi should just let you download the global venv

[daisy@cloudisland.nz]

@xssfox no wait

you have just one venv. total. for everyone. it’s on a network share that everyone has mounted, and if you pip install something it’s installed for everyone

all of your dependency management problems are solved when there is just one venv for everyone

⁃ collaborators’ environments drifting apart? one venv for everyone
⁃ tired of having to manage dependency updates in prod? one venv for everyone

you will not regret using one venv for everyone

[daisy@cloudisland.nz]

@xssfox ok sweet PyCon talk sorted

[xssfox@cloudisland.nz]

@daisy I love the implied solution to multiarch builds

[firstyear@infosec.exchange]

@daisy @xssfox isnt this just cpanel?