Re: Python CL Command Wrappers

Nowadays Python programmers tend to work in multiple virtual environments
... see module venv

This solves the "which python am I calling" as the venv you set up
determines what "python" means.

On Thu, Apr 25, 2019 at 8:27 PM John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Thu, Apr 25, 2019 at 5:52 PM Richard Schoen
<richard@xxxxxxxxxxxxxxxxx> wrote:

So I tested this and it appears that python and pthon2 call the same

thing - Python2. And python3 calls Python3.

Does that really need to change ?

"Need" is a strong word. It is easy enough to get around if it is
causing issues. My yum-only install doesn't have a plain "python" with
no number, that I know of.

I seem to recall 5733-OPS may have had the Python 2 installed as plain
"python", possibly also with "python2". I never had that on my system.

John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com