← Back to issue list

'snapcraft' and 'snapcraft-parser' need to use '#!/usr/bin/env python3' in the shebang line

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1602379
Type
issue
State
closed
Author
~joetalbott
Labels
Created
Updated
Closed

Current evaluation

⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.

Issue requesting '#!/usr/bin/env python3' shebang lines for 'snapcraft' and 'snapcraft-parser' was closed without comments or resolution details.

Suggested action:

No scores available.

Issue body

Both should use '#!/usr/bin/env python3'.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Issue requesting '#!/usr/bin/env python3' shebang lines for 'snapcraft' and 'snapcraft-parser' was closed without comments or resolution details.
qwen/qwen3.6-35b-a3b Closed without comments or resolution details. The request to update shebang lines in snapcraft and snapcraft-parser to python3 was not discussed, indicating it was resolved or abandoned.
qwen3.6-35b-a3b-mtp-q6 Closed as abandoned. The suggested shebang update to #!/usr/bin/env python3 for snapcraft and snapcraft-parser was not implemented.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1486680 snapcraft plugin for python2/3 should fix incorrect shebang on pkg_resources-generated scripts snapcraft (launchpad) closed Closed without resolution. The request to patch pkg_resources-generated shebangs from /usr/bin/python3 to /usr/bin/env python3 in the snapcraft plugin was abandoned.
77%
#1778716 snapcraft clean snapcraft fails as it cannot find python snapcraft (launchpad) closed Closed without comments or explicit resolution, likely abandoned or resolved in a later release. The bug reported a MissingPythonCommandError during snapcraft clean due to python3 path resolution ordering.
74%