regression on detection of python bin #126
Comments
mfussenegger
added a commit
that referenced
this issue
Feb 1, 2024
Should solve #126 Maybe this is good enough - another option would be to double check the if the python path exists, but that would add some extra workload.
mfussenegger
added a commit
that referenced
this issue
Feb 1, 2024
Should solve #126 Maybe this is good enough - another option would be to double check the if the python path exists, but that would add some extra workload.
|
Thanks for pointing out. I added an additional directory check: #128 If that still causes problem let me know - I'd have to add another check on the full python path |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the changes done in #121,
.envis used as one of the potential candidates for the directory containing python binary, however it is quite common used as file for storing environment variables that can be automatically sourced by different frameworks and tools. These include docker-compose, as well as python packages likepython-dotenv, or django.I would like to suggest a change that would check if the file found is a directory before actually trying to use it for python binary lookup.
The text was updated successfully, but these errors were encountered: