Post #3605900
2026-07-05 13:38 UTC
Replies (5)
-
@davidvujic@mastodon.nu 2026-07-05 14:20
@nedbat@hachyderm.io or maybe Local environment. Then a repo with many projects would make sense too 😁
-
@pfmoore@mastodon.social 2026-07-05 14:18
@nedbat@hachyderm.io Disagree. I use them all the time for things that aren't projects.
-
@flyingsaceur@ioc.exchange 2026-07-05 17:48
@nedbat@hachyderm.io that thing where they create a virtualenv in their home directory and install everything in it
-
@aes@toot.community 2026-07-05 18:10
@nedbat@hachyderm.io I understand why you'd prefer that name, but both are just word salad. That's bad because people turn their brains off for the following explanation, in a cognitive miser saccadic masking. Call it a Kerfuffle instead, and now everyone has to pay attention and form a new concept. Or not, but then the contract is whatever their idea of 'project' is.
-
@real_landru@fosstodon.org 2026-07-06 02:01
@nedbat@hachyderm.io I think "project environment" would help. Most of the option development where I work is small scripts or installed in a non standard location, with only a small amount in a pure python larger scale area. Getting through to the devs that they need a separate virtual environment on their vm, rather than installing RPMs into the system option, is a flight every time.