Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat] --python flag for grass79.py #703

Open
HuidaeCho opened this issue Jun 9, 2020 · 0 comments
Open

[Feat] --python flag for grass79.py #703

HuidaeCho opened this issue Jun 9, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@HuidaeCho
Copy link
Member

HuidaeCho commented Jun 9, 2020

Is your feature request related to a problem? Please describe.

In case there are multiple installations of Python, it would be great to be able to execute the version associated with the GRASS_PYTHON environment variable for batch jobs.

Describe the solution you'd like

It can be either --exec python (a special case of --exec; if the batch job command is python, run GRASS_PYTHON instead of one in PATH; it can be a surprise though if the user intended to use non-GRASS_PYTHON in PATH, but why?) without adding a new flag, or --python path/to/script.py args... (better? but yet another flag).

Describe alternatives you've considered

Just leave it to the user. --exec /path/to/grass/python3 script.py args... with no changes.

Additional context

I encountered this issue while writing the workflow script for OSGeo4W (#692). There were two python installations from OSGeo4W (GRASS_PYTHON) and MSYS2, but MSYS2's path was in front of OSGeo4W by default. I had to specify the full path to the OSGeo4W python.

@HuidaeCho HuidaeCho added the enhancement New feature or request label Jun 9, 2020
@HuidaeCho HuidaeCho changed the title [Feat] --python flag for grass79.py [Feat] --python flag for grass79.py Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant