Merge lp:~yashi/snapcraft/snapcraft into lp:~snappy-dev/snapcraft/core
Status: | Superseded |
---|---|
Proposed branch: | lp:~yashi/snapcraft/snapcraft |
Merge into: | lp:~snappy-dev/snapcraft/core |
Diff against target: |
12 lines (+1/-1) 1 file modified
snapcraft/plugins/python3_project.py (+1/-1) |
To merge this branch: | bzr merge lp:~yashi/snapcraft/snapcraft |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Snappy Developers | Pending | ||
Review via email: mp+272337@code.launchpad.net |
This proposal has been superseded by a proposal from 2015-10-02.
Description of the change
This fixes snapcraft on wily with multiple supported python version, lp:#1499429. The patch takes the least supported version, 3.4, because scanpcraft did not work with python 3.5 on my wily yet.
Unmerged revisions
- 210. By Yasushi SHOJI
-
Handle multiple supported-versions returned by pyversions and py3versions
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.5pyversions, with /usr/share/
python/ debian_ defaults, behaves the same. `pyversions -i` and `py3version -i` is used in snapcraft to generate
PYTHONPATH in Python3ProjectPlugin:: python_ version( ), but due to the
multiple return values separated by a space, it generates the
following PYTHONPATH:"....spongesha
ker/install/ usr/lib/ python3. 4 python3. 5/dist- packages" and dies with "export: python3.
5/dist- packages: bad variable name". To fix this, just take the first entry of the list. It's usually the
oldest supported version available and safer to rely on.
This works but it's a bit weird. Unless there's something I'm missing I'd just use this:
>>> 'python3.4 python3.5'.split()
['python3.4', 'python3.5']
So personally I'd remove the (None, 1) arguments