Bug 1269952
Summary: | python scripts using #!/usr/bin/env python shebang will be affected by python3 default interpreter in Fedora 23. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Goutam Kodu <goutamkk> |
Component: | python3 | Assignee: | Charalampos Stratakis <cstratak> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | bkabrda, gaurav.sood, goutamkk, jberan, pviktori, rkuska, tomspur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-02-01 08:46:27 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Goutam Kodu
2015-10-08 14:51:24 UTC
Hi, Can somebody update what is the resolution for this bug ? Will there be python file soft linked to python3 ? Thanks, Goutam The current upstream recommendation is that "python" should mean Python 2 (see [PEP 394]). As with any script, you need to install the interpreter that can run it – in this case, Python 2. Alternatively, you can change the shebang to "#!/usr/bin/env python3". A shebang that would somehow automatically choose between py2 and py3 is being discussed upstream: https://mail.python.org/pipermail/linux-sig/2015-October/000000.html [PEP 394]: https://www.python.org/dev/peps/pep-0394/ This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Hello Goutam, Did that answer your question, or do you need any more info? Yes Petr that answered my question. Sorry for delay in my response. We updated the code with "#!/usr/bin/env python3" shebang thanks, Goutam Thanks for the reply. I'll close the bug, but get in touch if anything else is unclear. |