Re: Defeat Python "Virtual Environment" in Fedora ?

On 2026-03-09, c186282 <[email protected]> wrote:
> On 3/8/26 23:55, Lawrence D’Oliveiro wrote:
>> On Mon, 09 Mar 2026 02:47:51 GMT, Charlie Gibbs wrote:
>>> I did write a little Python program that played with the various GUI
>>> gadgets that it made available (with much less effort than doing it
>>> in C). It made me think that I could write something that my wife
>>> might actually be able to use. (I was careful to use Python 3, not
>>> 2.) It would be nice if this remained a viable option; otherwise
>>> it's back to writing Yet Another C Program.
>> 
>> C would only be better if you could somehow get by with fewer
>> dependencies than with the Python equivalent. I’m not sure how you
>> would manage that -- reinvent more of your own wheels, perhaps?
>
>    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.

Python virtual environments do nothing whatsoever to stop you calling
whatever you like with "os.system()". A Python "virtual environment"
is simply a separate set of installed third-party library packages,
to avoid conflicts between the packages used by your program and
those used by other programs. You seem to be under the false impression
that it's some sort of chroot/jail/sandbox, and it simply isn't.
Python has no sandbox feature.