apamacommunity / pysys-vscode-extension Goto Github PK

From within a PySys project there is the option to run

python -m pysys print

In fact this can be done at various levels within the project to narrow down the output

We should add a right click menu option to run this command on all nodes of the tree (root/directory...)

We could add an info option to the test its self so an "info" icon - provides the output for that test alone:

add 2 hard coded options to the right click menu

• validate only
• run debug

Additionally and to add further flexibility we should allow custom runs for individual tests to allow arbitrary args to be passed on the run of a single test.

This will add extra tasks to the tasks.json but will allow the most flexibility.

• Capitalize PySys where appropriate
• Improve the doc description and initial Readme intro:

• "Instead of linking to pypi, best to link to https://pysys-test.github.io/pysys-test/"

To help the user we should allow them to override the default python on the path with their own choice.
This should be explicitly overridden not set by default.

These settings will replace the default command used when invoking commands. Where we currently use

python -m pysys

If the python executable is set to be

/mypath/bin/python or c:\myWindowsPath\bin\python.exe we should use these

/mypath/bin/python -m pysys ...

When we build the list of directories to show/traverse/watch we should

• Ignore directories containing pysysignore or .pysysignore
• any directory starting with __

filesystem watchers have the ability to add extra regexes for things to omit from the results, if we are searching using other methods (I think we are) then we will need to code some logic to skip these

I tried to run a test from a set when I toggled flat mode and it failed to run.

• New to re-add the check for Python on the path and PySys - if they are missing then show message
• The output window should show python path (which python or windows equivilent) and the versions that will be used by the extension
• Possibly add a text node to the PySys project view to indicate missing dependencies

When the extesion starts it should check for the variations on python that might allow it to work:

• default = python -m pysys
• python3 -m pysys
• py -3 -m pysys
• others?

If none work we need to produce output/popup saying why and that the user should install python and or pysys - possibly giving links/ commands (python -m pip install pysys)

Note pysys 1.6 has a dependency on python 3.7+

So additionally we might want to consider on a version of python less than that suggesting upgrade to 3.7/pysys 1.6

The Python installation detection in getPysysInterpreter() is looking for ersion in the output from the -V option to the Python interpreter. However, all the Python interpreters I have available produce output of the form Python x.y.z, e.g.

scott@orac:~/Projects$ python3 -V
Python 3.7.4
scott@orac:~/Projects$ python2 -V
Python 2.7.17

This is on WSL2 Ubuntu 18.04 and Raspberry Pi OS December 2020, using Pythons from the standard repos, so I don't think there is anything weird going on in my environment. I've opened PR #21 to (maybe) fix this and a related issue I found while trying to debug the first one.