Bug 1797686 - python-parver fails to build with Python 3.9: imports abc from collections
Summary: python-parver fails to build with Python 3.9: imports abc from collections
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: python-parver
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON39
TreeView+ depends on / blocked
 
Reported: 2020-02-03 16:25 UTC by Miro Hrončok
Modified: 2020-02-28 09:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-28 09:08:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github RazerM parver pull 4 0 None open Drop Python 2 compatibility: Import abstract base classes from collections.abc 2020-02-03 17:07:09 UTC
Github RazerM parver pull 5 0 None open Try importing abstract base classes from collections.abc to support Python 2.7 to 3.9 2020-02-03 17:07:09 UTC

Description Miro Hrončok 2020-02-03 16:25:59 UTC
python-parver fails to build with Python 3.9.0a3.

___________________ ERROR collecting tests/test_packaging.py ___________________
ImportError while importing test module '/builddir/build/BUILD/parver-0.1.1/tests/test_packaging.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests/test_packaging.py:16: in <module>
    from parver import ParseError, Version
../../BUILDROOT/python-parver-0.1.1-6.fc32.x86_64/usr/lib/python3.9/site-packages/parver/__init__.py:6: in <module>
    from ._version import Version
../../BUILDROOT/python-parver-0.1.1-6.fc32.x86_64/usr/lib/python3.9/site-packages/parver/_version.py:7: in <module>
    from collections import Sequence
E   ImportError: cannot import name 'Sequence' from 'collections' (/usr/lib64/python3.9/collections/__init__.py)
_____________________ ERROR collecting tests/test_parse.py _____________________
ImportError while importing test module '/builddir/build/BUILD/parver-0.1.1/tests/test_parse.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests/test_parse.py:7: in <module>
    from parver import ParseError, Version
../../BUILDROOT/python-parver-0.1.1-6.fc32.x86_64/usr/lib/python3.9/site-packages/parver/__init__.py:6: in <module>
    from ._version import Version
../../BUILDROOT/python-parver-0.1.1-6.fc32.x86_64/usr/lib/python3.9/site-packages/parver/_version.py:7: in <module>
    from collections import Sequence
E   ImportError: cannot import name 'Sequence' from 'collections' (/usr/lib64/python3.9/collections/__init__.py)
____________________ ERROR collecting tests/test_version.py ____________________
ImportError while importing test module '/builddir/build/BUILD/parver-0.1.1/tests/test_version.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests/test_version.py:7: in <module>
    from parver import Version
../../BUILDROOT/python-parver-0.1.1-6.fc32.x86_64/usr/lib/python3.9/site-packages/parver/__init__.py:6: in <module>
    from ._version import Version
../../BUILDROOT/python-parver-0.1.1-6.fc32.x86_64/usr/lib/python3.9/site-packages/parver/_version.py:7: in <module>
    from collections import Sequence
E   ImportError: cannot import name 'Sequence' from 'collections' (/usr/lib64/python3.9/collections/__init__.py)
!!!!!!!!!!!!!!!!!!! Interrupted: 3 errors during collection !!!!!!!!!!!!!!!!!!!!
=========================== 3 error in 0.23 seconds ============================

See https://docs.python.org/3.9/whatsnew/3.9.html#removed

"The abstract base classes in collections.abc no longer are exposed in the regular collections module. This will help create a clearer distinction between the concrete classes and the abstract base classes."



For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01219829-python-parver/

For all our attempts to build python-parver with Python 3.9, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/python-parver/

Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.9:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/

Let us know here if you have any questions.

Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Miro Hrončok 2020-02-03 16:29:50 UTC
parver 0.2.1 is available (bz1697361) but I see "from collections import Sequence" in the master branch, so that would not fix the issue.

Comment 2 Miro Hrončok 2020-02-03 17:07:09 UTC
Upstream PR:

drop python 2 support: https://github.com/RazerM/parver/pull/4
keep python 2 support: https://github.com/RazerM/parver/pull/5

Comment 3 Ben Cotton 2020-02-11 17:20:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 4 Miro Hrončok 2020-02-28 09:08:33 UTC
In Python 3.9.0a4 we have managed to revert the change that disables importing abstract base classes (collections.abc) directly form the regular collections module. It was reverted to ease transition for projects that did not yet actually dropped support for Python 2.7. The removal is scheduled for Python 3.10 instead.

We are mass closing all the bug reports about build failures that were caused by this. Expect a new Bugzilla report in case this package fails to build with Python 3.9 for a different reason as well.

In case you haven't done this already, we highly recommend to talk to your upstream and get this fixed anyway, because this will return in Python 3.10 and Python upstream is very unlikely to postpone this once more. In case you've already done that, thank you (this message is mass posted to all the relevant Bugzillas).


Note You need to log in before you can comment on or make changes to this bug.