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
Bug 1899278 - python-zodbpickle fails to build with Python 3.10: ImportError: cannot import name 'TESTFN' from ''
Summary: python-zodbpickle fails to build with Python 3.10: ImportError: cannot import...
Alias: None
Product: Fedora
Classification: Fedora
Component: python-zodbpickle
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: PYTHON3.10
TreeView+ depends on / blocked
Reported: 2020-11-18 19:42 UTC by Miro Hrončok
Modified: 2020-11-18 23:55 UTC (History)
3 users (show)

Fixed In Version: python-zodbpickle-2.0.0-6.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-11-18 23:55:29 UTC
Type: Bug

Attachments (Terms of Use)

Description Miro Hrončok 2020-11-18 19:42:22 UTC
python-zodbpickle fails to build with Python 3.10.0a2.

Traceback (most recent call last):
  File "/builddir/build/BUILD/zodbpickle-2.0.0/", line 45, in <module>
  File "/usr/lib/python3.10/site-packages/setuptools/", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib64/python3.10/distutils/", line 148, in setup
  File "/usr/lib64/python3.10/distutils/", line 966, in run_commands
  File "/usr/lib64/python3.10/distutils/", line 985, in run_command
  File "/usr/lib/python3.10/site-packages/setuptools/command/", line 232, in run
  File "/usr/lib/python3.10/site-packages/setuptools/command/", line 250, in run_tests
    test = unittest.main(
  File "/usr/lib64/python3.10/unittest/", line 100, in __init__
  File "/usr/lib64/python3.10/unittest/", line 147, in parseArgs
  File "/usr/lib64/python3.10/unittest/", line 158, in createTests
    self.test = self.testLoader.loadTestsFromNames(self.testNames,
  File "/usr/lib64/python3.10/unittest/", line 220, in loadTestsFromNames
    suites = [self.loadTestsFromName(name, module) for name in names]
  File "/usr/lib64/python3.10/unittest/", line 220, in <listcomp>
    suites = [self.loadTestsFromName(name, module) for name in names]
  File "/usr/lib64/python3.10/unittest/", line 205, in loadTestsFromName
    test = obj()
  File "/builddir/build/BUILD/zodbpickle-2.0.0/src/zodbpickle/tests/", line 27, in test_suite
    from .test_pickle_3 import test_suite
  File "/builddir/build/BUILD/zodbpickle-2.0.0/src/zodbpickle/tests/", line 7, in <module>
    from .pickletester_3 import AbstractPickleTests
  File "/builddir/build/BUILD/zodbpickle-2.0.0/src/zodbpickle/tests/", line 10, in <module>
    from import (
ImportError: cannot import name 'TESTFN' from '' (/usr/lib64/python3.10/test/support/ is an internal module with no stable API, TESTFN got removed:

As a stop gap measure, it can be imported from instead (still internal and unstable).

For the build logs, see:

For all our attempts to build python-zodbpickle with Python 3.10, see:

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.10:

Let us know here if you have any questions.

Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
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 Jerry James 2020-11-18 23:55:29 UTC
There were a few more problems, all fixed now in Rawhide.  Upstream already filed its own tracking bug for python 3.10, so all issues will hopefully be addressed upstream soon.

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