← Back to issue list

snapcraft dies with "export: python3.5/dist-packages: bad variable name"

View original Launchpad issue

Metadata

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

Current evaluation

Closed without resolution due to inactivity. Snapcraft crashes when py3versions returns multiple Python versions, generating a malformed PYTHONPATH that breaks the export command.

Suggested action:

No scores available.

Issue body

On Wily with python3-minimal 3.4.3-4ubuntu1, /usr/share/python3/debian_defaults has multiple version listed in supported-versions. supported-versions = python3.4, python3.5 Those versions return when `py3version -i` is run. $ py3versions -i python3.4 python3.5 py3version -i is used in snapcraft to generate PYTHONPATH in Python3ProjectPlugin::python_version(), but due to the return value of py3version, and the value has space in it, it generates the following PYTHONPATH and dies with "export: python3.5/dist-packages: bad variable name". "....spongeshaker/install/usr/lib/python3.4 python3.5/dist-packages"

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without resolution due to inactivity. Snapcraft crashes when py3versions returns multiple Python versions, generating a malformed PYTHONPATH that breaks the export command.
qwen/qwen3.6-35b-a3b Closed without resolution. py3versions returning multiple Python versions caused a malformed PYTHONPATH export. With zero comments and over a decade of inactivity, the issue was abandoned as the affected Ubuntu and Python versions are obsolete.
qwen/qwen3.6-35b-a3b Abandoned. Snapcraft crashed when py3versions returned multiple Python versions, creating a malformed PYTHONPATH export with unquoted spaces.
qwen3.6-35b-a3b-mtp-q6 Reported a snapcraft crash when py3versions -i returns multiple Python versions, creating a malformed PYTHONPATH export. Closed without comments or a patch, indicating the bug was abandoned.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#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.
77%
#1862163 snapcraft breaks with python app snapcraft (launchpad) closed Closed without resolution. Snapcraft auto-generated invalid command paths starting with `/` for Python apps, causing snapd validation failures. No fix, discussion, or follow-up was provided.
76%
#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.
72%
#1875872 snapcraft crashes whenever I try to run it snapcraft (launchpad) closed Closed. Resolved by replacing the deprecated platform.dist() call with a supported platform API to fix the AttributeError crash on newer Python versions.
71%
#1587193 build of python3 snap fails with 'error: option --single-version-externally-managed not recognized' snapcraft (launchpad) closed Closed without resolution. The snapcraft pip flag compatibility issue was abandoned due to inactivity and likely superseded by updated snapcraft and pip versions.
71%
#4300 snapcraft fails for python projects if there is no setup.py snapcraft closed Closed as stale due to inactivity. Maintainers identified the failure as a missing entry_points or scripts configuration in pyproject.toml, not a snapcraft bug.
71%