On Wednesday, 2 March 2022 11:46:15 EST Chris Albertson wrote:
> Yes, whoever writes the Phython code needs to place the requirements
> in a file called "requirements.text" and make a setup.py file.
>
> This is not the place to discuss software development best-practices.
> It is best to read
Yes, whoever writes the Phython code needs to place the requirements in a
file called "requirements.text" and make a setup.py file.
This is not the place to discuss software development best-practices. It
is best to read the Python documentation and follow it to the letter.
What they suggest is
On Wednesday, March 2, 2022 4:14:48 AM EST Karl Jacobs wrote:
> To correct typos, that should rather read
> "python3.7 -m venv "
> and
> "source /bin/activate"
> to create and activate a python virtual environment, in this case with
> the specific python version 3.7 that you want to use (which of
To correct typos, that should rather read
"python3.7 -m venv "
and
"source /bin/activate"
to create and activate a python virtual environment, in this case with
the specific python version 3.7 that you want to use (which of course
must be installed and in your $PATH). If you just say python3, the
It is easy to install 3.7 First use "python3 -m vend " then
"source /bin/activate" then install the version of
python you like and whatever version of the packages you want. That's it.
Now you have a vertical environment.
In fact, almost every Python developer does this is it is generally a
Greetings all;
Any progress on that? The python is too new. Buster is just fine with its
python-3.7, but bullseye has python-3.9.2 and breaks it.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed