Bluebird added the comment:
Ok, I'll close my request if you do not think of any value in it.
Py is such an elegant solution, I wish something as simple would also address
this problem.
Virtual environement do have the downside of not coming directly with Python.
In my work environment, ex
Steve Dower added the comment:
> Create a pyscript launcher, which would work like py but would take as
> command-line the name of the script to run ...
This is spelled "py [-x.y] -m [script]", but it's up to the libraries to
support it. We can't force them to do it.
> Let py execute a comm
Steve Dower added the comment:
> Moreover, some of these C++ exectuables depends on DLL which are only in the
> Scripts directory and it might not work.
In this case, perhaps these tools should be in a separate directory? A simple
.py script could be added to Scripts that works with "-m" and
Bluebird added the comment:
Thanks for the quick feedback.
I agree that it makes sense for python modules to support -m. However, PyQt
comes with many executables originally written in C++ for Qt (designer,
assistant). It feels a bit strange to add a module with that name, just for the
purp
Paul Moore added the comment:
Most items in the Scripts directory can be run using the `-m` flag to Python,
so you can use something like `py -m pip` to run pip without needing the
Scripts directory in PATH.
If an individual project like PyQt doesn't support -m, it's relatively easy for
the
New submission from Bluebird :
The py Python launcher is a great improvement over a few years ago when
managing multiple Python installation was tedious.
However, it does not solve one annoying problem: the Scripts directory. If you
install tools like mypy, pyqt-tools or pyinstaller, to be ab
