Re: Defeat Python "Virtual Environment" in Fedora ?

Pancho <[email protected]> Fri, 13 Mar 2026 09:34:06 +0000
Newsgroups comp.os.linux.misc,comp.lang.python
Organization A noiseless patient Spider
Message-ID <[email protected]>
On 3/12/26 10:39, Nuno Silva wrote:
> On 2026-03-11, Pancho wrote:
> 
>> On 3/10/26 18:14, Piergiorgio Sartor wrote:
>>> On 10/03/2026 18.03, c186282 wrote:
>>> [...]
>>>>     Can't figure out how to zap the VENV in order
>>>>     to provide the examples you'd like  :-)
>>>
>>> There are the following possibilities here:
>>> 1) You didn't properly get what a venv is in Python
>>> 2) You're trolling.
>>>
>>> Assuming 1), the venv is nothing more that a
>>> search path change, for Python programs and
>>> modules. Where, instead of looking first into
>>> the system folders, first is searched in the
>>> venv "repository" area.
>>> Nothing more, nothing less.
>>>
>>
>> My understanding is different. My understanding is that a venv only
>> uses packages installed locally in the venv.  It shouldn't default to
>> a global package if it is not found in the venv.
> 
> I guess the other view is to allow package management to exist and work,
> and using venvs only for what can't be managed by the package manager...
> 

I want my programs to work on different machines, and to continue to 
work over time. I don't care how that happens, maybe you can achieve 
that with package managers. The problem is a quick Goole tells me DLL 
Hell was solved with assemblies, so my nightmares with the GAC must have 
been an illusion.

In effect, it might be true, but I'll take that with a pinch of salt. I 
often find Python apps have problems, so it seems other people have 
problems too.



>> (caveat: it may use default site installed packages if told to do so).
> 
> ... but then I guess that's what stuff managed by the package manager
> ends up as?
> 
>> This is very much what I would want. I would want my python app to
>> work independently of some eccentricity of the machine I develop on. I
>> suspect if I were still a developer I would go further and use
>> snaps,flatpak, or docker containers.
> 
> At this point, why not also use static linking?
> 

I remember being excited by .so files in Solaris, circa 1994, about the 
time I bought a 1GB hdd. i.e. Storage constraints have changed.

Also, there have been a lot of os (running environment) advances with 
respect to sharing duplicated stored data. Mainly I don't want to know, 
it is something a computer can manage better than I can. I just don't 
want applications built on quicksand libraries.