starting phase `patch-source-shebangs' patch-shebang: ./docs/conf.py: warning: no binary for interpreter `python3' found in $PATH patch-shebang: ./pkg_resources/_vendor/appdirs.py: changing `/usr/bin/env python' to `/gnu/store/ln0jd0k32xbr2jyha1sdaynllkazgmsi-python2-2.7.17/bin/python' patch-shebang: ./setup.py: changing `/usr/bin/env python' to `/gnu/store/ln0jd0k32xbr2jyha1sdaynllkazgmsi-python2-2.7.17/bin/python' phase `patch-source-shebangs' succeeded after 0.0 seconds starting phase `patch-generated-file-shebangs' phase `patch-generated-file-shebangs' succeeded after 0.0 seconds starting phase `build' running "python setup.py" with command "build" and parameters () Traceback (most recent call last): File "<string>", line 1, in <module> File "setuptools/__init__.py", line 16, in <module> import setuptools.version File "setuptools/version.py", line 1, in <module> import pkg_resources File "pkg_resources/__init__.py", line 1367 raise SyntaxError(e) from e ^ SyntaxError: invalid syntax command "python" "-c" "import setuptools, tokenize;__file__='setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\\r\\n', '\\n');f.close();exec(compile(code, __file__, 'exec'))" "build" failed with status 1
Hi, On Wed, 27 Jan 2021 at 08:47, "K I" <gitlabcanada@runbox.com> wrote: > File "pkg_resources/__init__.py", line 1367 > raise SyntaxError(e) from e > ^ > SyntaxError: invalid syntax > command "python" "-c" "import setuptools, tokenize;__file__='setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\\r\\n', '\\n');f.close();exec(compile(code, __file__, 'exec'))" "build" failed with status 1 It is expected because Setuptools removed the compatibility with Python 2, see the ChangeLog: --8<---------------cut here---------------start------------->8--- v47.0.0 28 May 2020 Breaking Changes #2094: Setuptools now actively crashes under Python 2. Python 3.5 or later is required. Users of Python 2 should use setuptools<45. --8<---------------cut here---------------end--------------->8--- <https://setuptools.readthedocs.io/en/latest/history.html> <https://github.com/pypa/setuptools/issues/2094> The question is: do we remove ’python2-setuptools’ since it is defined by the usual ’package-with-python2’? --8<---------------cut here---------------start------------->8--- (define-public python2-setuptools (package-with-python2 python-setuptools)) --8<---------------cut here---------------end--------------->8--- Or do we define python2-setuptools with the version v46.4.0? Which, IMHO does not make sense since Python 2 is end of life since one year. All the best, simon
Hi,
On Thu, 28 Jan 2021 at 02:09, zimoun <zimon.toutoune@gmail.com> wrote:
> On Wed, 27 Jan 2021 at 08:47, "K I" <gitlabcanada@runbox.com> wrote:
>
>> File "pkg_resources/__init__.py", line 1367
>> raise SyntaxError(e) from e
>> ^
>> SyntaxError: invalid syntax
>> command "python" "-c" "import setuptools, tokenize;__file__='setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\\r\\n', '\\n');f.close();exec(compile(code, __file__, 'exec'))" "build" failed with status 1
>
> It is expected because Setuptools removed the compatibility with Python 2,
> see the ChangeLog:
>
> v47.0.0
>
> 28 May 2020
> Breaking Changes
>
> #2094: Setuptools now actively crashes under Python 2. Python 3.5 or later is required. Users of Python 2 should use setuptools<45.
>
>
> <https://setuptools.readthedocs.io/en/latest/history.html>
> <https://github.com/pypa/setuptools/issues/2094>
>
>
> The question is: do we remove ’python2-setuptools’ since it is defined
> by the usual ’package-with-python2’?
>
> (define-public python2-setuptools
> (package-with-python2 python-setuptools))
>
> Or do we define python2-setuptools with the version v46.4.0? Which,
> IMHO does not make sense since Python 2 is end of life since one year.
Currently, python-setuptools is at version 52.0 and python2-setuptools
at version 41.0.1. Both build fine. The comment says:
--8<---------------cut here---------------start------------->8---
;; Newer versions of setuptools no longer support Python 2.
(define-public python2-setuptools
(package
(name "python2-setuptools")
(version "41.0.1")
--8<---------------cut here---------------end--------------->8---
therefore, this part of the bug is done. Let check the other part.
Cheers,
simon