Re: Defeat Python "Virtual Environment" in Fedora ?

On 3/10/26 13:09, Jon Ribbens wrote:
> On 2026-03-10, c186282 <[email protected]> wrote:
>> On 3/10/26 10:55, Rich wrote:
>>> In comp.os.linux.misc c186282 <[email protected]> wrote:
>>>> On 3/9/26 09:59, Richard Kettlewell wrote:
>>>>> c186282 <[email protected]> writes:
>>>>>>      The Python VENV *seems* to be thwarting my
>>>>>>      ability to run certain hard-core system
>>>>>>      routines via "os.system()" or related. The
>>>>>>      'virtual' seems to be for idiot 7-year-olds
>>>>>>      you don't want to crash the box.
>>>>>>
>>>>>>      Well, sometimes, I *want* to crash the box.
>>>>>
>>>>> As Jon says, you’ve misdiagnosed your problem.
>>>>
>>>>     COULD be ...
>>>>
>>>>     But I still note that things that worked clean
>>>>     and easy pre-VENV now DON'T.
>>>>
>>>>     Who/what should I blame ?
>>>>
>>>>     There's no POINT in a 'virtual environment/machine'
>>>>     unless you PLAN to isolate the base machine from
>>>>     the application to various degrees.
>>>>
>>>>> If you actually want someone to help solve your problem then you’ll have
>>>>> to accurately describe what you are trying and what is happening. In
>>>>> practice this means posting the exact code you are using and exactly
>>>>> what happens when you run it.
>>>>
>>>>     Too fuckin' old now, not gonna get into a million
>>>>     details and sub-sub-sub-config-files. I just report
>>>>     that some lower-level OS commands no longer work
>>>>     as expected, or at all, using the usual Python
>>>>     utilities for doing so.
>>>>
>>>>     I want the VENV *dead* ... CAN that be done ???
>>>
>>> And, again, much as Jon said, you are blaming "venv's" but given us no
>>> examples to support your assertion.  It is *very likely* that you
>>> indeed are blaming the wrong thing.  How about creating a very short
>>> example that works without a venv but fails within one, and posting
>>> that example.  That will give others, who may know far more python than
>>> you do, something to analyze and maybe show you where the problem
>>> really exists.
>>
>>     Can't figure out how to zap the VENV in order
>>     to provide the examples you'd like  :-)
>>
>>     Seems like, of late, it's entirely baked-in -
>>     Python is the VENV and the VENV is Python.
> 
> This not only isn't true, it cannot be true, because *by definition*
> if the environment you're seeing is the same one Python always sees
> then it isn't a "virtual" environment, it's the system environment.


   OK, tomorrow, HOW do I start a Py3 that's NOT in
   the VENV ???

   Go ahead, search - I have. All the 'fixes' don't
   work anymore.

   Many say "no problem" - yet NO current workarounds.