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
Use "/usr/bin/env python3" consistently for Python3 scripts #788
Comments
This was fixed as a part of this PR: #789 I think we can go ahed and close this. |
Looks like some might be missed. Running this against the repo:
Shows some default python in use:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One of the workarounds for #764 is to set up a /usr/bin/python link so that
#!/usr/bin/env python
can find something to use as its interpreter.Within the scripts, the use of
#!/usr/bin/env
is inconsistent. In some scripts we have this old config which requires the set-alternatives workaround:#!/usr/bin/env python
. This is present even in the "ported to Python 3" directory. For example:PowerShell-DSC-for-Linux/Providers/Scripts/3.x/Scripts/nxArchive.py
Line 1 in 9f6301f
In other places, there's the more explicit and will-work-on-RHEL8-by-default
#!/usr/bin/env python3
:PowerShell-DSC-for-Linux/Providers/Scripts/3.x/Scripts/nxAvailableUpdates.py
Line 1 in 9f6301f
It seems like since
#!/usr/bin/env python3
is already in use in some scripts, it would make sense to configure this as the default for all of the scripts in the 3.x directory. This appears to already be the case for the set of scripts inProviders/nxOMSAutomationWorker/automationworker/3.x
with the odd exceptions ofworker/__init__.py
andworker/importHelper.py
The text was updated successfully, but these errors were encountered: