A couple of minor suggestions
Brought to you by:
thewatcher2018
Menu
▾
▴
#4 A couple of minor suggestions
I think this is a great idea. Some things assume specific versions of Python, some are not compatible with newer ones. Particularly a problem with stuff for Python 2.7 (there was a while some devs were stubbornly refusing to change to 3 entirely in fact.) This software actually has a huge use case in that it can basically guarantee it will be possible to get even older scripts to continue working into the future. There are just two things I'd like to suggest:
-
The console launcher should modify the path variable to include the scripts folder. Pretty much just as simple as a line "SET PATH=%CD%\App\Python\Scripts;%PATH%" or whatever the equivalent would be. Not only would this clear up an annoying error, but since it's not in the path, one can't just simply cd to another directory and type the script in a different folder but you must prefix it with the full pathname to where the script's .exe actually is.
-
Of course it makes sense the base package would not include extra libraries, but it can be hard to actually install older libraries as well as a number of incompatibilities. Eventually it may become impossible or prohibitively difficult even to get a meaningfully working environment for some things. I think it would be useful if there were external and entirely optional packages that include at least a few common libraries (like PyUsb just off the top of my head as an example.) Obviously it couldn't include an exhaustive "everything" list, but at least a lot of the more commonly used things could be useful. The further one goes back, the longer the list of errors gets just trying to install via pip.
As a bit of a correction to #1, I found the start_script.cmd file which apparently would actually do that except that for some reason the line is remarked out. So I guess it's as simple as removing the REM from that line.