Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1794341 - python-spyder-kernels fails to build with Python 3.9: imports abc from collections
Summary: python-spyder-kernels fails to build with Python 3.9: imports abc from collec...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: python-spyder-kernels
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mukundan Ragavan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON39
TreeView+ depends on / blocked
 
Reported: 2020-01-23 10:41 UTC by Miro Hrončok
Modified: 2020-02-28 09:07 UTC (History)
4 users (show)

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

Attachments (Terms of Use)

Description Miro Hrončok 2020-01-23 10:41:27 UTC 
python-spyder-kernels fails to build with Python 3.9.0a2.

ImportError: Failed to import test module: iofuncs
Traceback (most recent call last):
  File "/usr/lib64/python3.9/unittest/loader.py", line 154, in loadTestsFromName
    module = __import__(module_name)
  File "/builddir/build/BUILD/spyder-kernels-0.5.2/spyder_kernels/utils/iofuncs.py", line 44, in <module>
    from spyder_kernels.py3compat import getcwd, pickle, PY2, to_text_string
  File "/builddir/build/BUILD/spyder-kernels-0.5.2/spyder_kernels/py3compat.py", line 79, in <module>
    from collections import MutableMapping
ImportError: cannot import name 'MutableMapping' from 'collections' (/usr/lib64/python3.9/collections/__init__.py)

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/01173234-python-spyder-kernels/

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

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 Karthikeyan Singaravelan 2020-01-24 03:59:11 UTC 
Seems to be fixed : https://github.com/spyder-ide/spyder-kernels/commit/de52b0686ccc8f74f39710a14ed032beb1b7a380
Comment 2 Mukundan Ragavan 2020-01-24 10:55:49 UTC 
I will update this when I update spyder to version 4 (Waiting on pathtools - https://bugzilla.redhat.com/show_bug.cgi?id=1770859)
Comment 3 Ben Cotton 2020-02-11 17:26:23 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:07:16 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.