From: "Andrew M.A. Cater" <amaca...@einval.com> Date: Thu, 27 Jul 2023 07:28:25 +0000 Message-id: <ZMIcmarb0/RGCR/9...@einval.com> In-reply-to: <[🔎] CAEG4cZXBJ3CbFUN1LuRQsKR=xjkzuw92lxlnrxwkxae-ery...@mail.gmail.com> References: <[🔎] CAEG4cZXe=BUQ5VE_z0rcLqHGGERdANnZ=vjiznjbk439jif...@mail.gmail.com> and the rest [ ... ]
Dear Mr. Cater, I thank you for writing a few lines to express your empathy. I understand everyone's limitations as well as mine. Hopefully, I will try to solve the issue or bypass it. [ ... ] >> >> Yes, a virtual environment (i.e., virtualisation) however is an idea >> >> that could theoretically be looked into, but that would mean extra >> >> system resources to be spent for it. >> > > > This is where terminology is not helpful. Python has the concept of > a virtual environment (venv) in which to run Python programs separately > from the Python installed as the system version - a very simple sandbox, > I think. > > I don't program in Python so I can't help much further but that's very > different from a full virtualised environment of a Linux machine - kvm / > qemu > or similar - which is very different and mor resource hungry. > [ ... ] Thank you Mr. Cater, especially for the above lines. You helped me understand that there are two virtualisation environments available, one being the entire virtualised Hardware environment via QEMU, VMware, VirtualBox, et al, and the other being only the Python virtual environment. I hope my senior list members will educate some more on this aspect. Best wishes, Rajib
