Bug 2276581 - python-cclib fails to build with Python 3.13: AttributeError: module 'unittest' has no attribute 'makeSuite'
Summary: python-cclib fails to build with Python 3.13: AttributeError: module 'unittes...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: python-cclib
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Antonio T. sagitter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.13
TreeView+ depends on / blocked
 
Reported: 2024-04-23 08:00 UTC by Karolina Surma
Modified: 2024-04-23 08:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karolina Surma 2024-04-23 08:00:50 UTC
python-cclib fails to build with Python 3.13.0a6.

+ /usr/bin/python3 -m test.test_data
/builddir/build/BUILD/cclib-8e6892a562b7916a465a808e2fce43ca7688592b/cclib/method/volume.py:17: SyntaxWarning: invalid escape sequence '\p'
  """ In the dictionary sym2powerlist below, each element is a list that contain the combinations of
/builddir/build/BUILD/cclib-8e6892a562b7916a465a808e2fce43ca7688592b/cclib/parser/gaussianparser.py:296: SyntaxWarning: invalid escape sequence '\s'
  match = re.search('NQMF=\s*(\d+)', line)
<frozen runpy>:128: RuntimeWarning: 'test.test_data' found in sys.modules after import of package 'test', but prior to execution of 'test.test_data'; this may result in unpredictable behaviour

*** basicDALTON-2013/dvb_sp_hf.out: Generic basis set unittest ***
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/builddir/build/BUILD/cclib-8e6892a562b7916a465a808e2fce43ca7688592b/test/test_data.py", line 337, in <module>
    test_all(parsers, modules, terse=args.terse, silent=args.silent, loglevel=loglevel, summary=True, visual_tests=True)
    ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/builddir/build/BUILD/cclib-8e6892a562b7916a465a808e2fce43ca7688592b/test/test_data.py", line 302, in test_all
    errors_or_failures = data_suite.testall()
                         ~~~~~~~~~~~~~~~~~~^^
  File "/builddir/build/BUILD/cclib-8e6892a562b7916a465a808e2fce43ca7688592b/test/test_data.py", line 193, in testall
    myunittest = unittest.makeSuite(test)
                 ^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.13/unittest/__init__.py", line 80, in __getattr__
    raise AttributeError(f"module {__name__!r} has no attribute {name!r}")
AttributeError: module 'unittest' has no attribute 'makeSuite'

According to https://docs.python.org/3.13/whatsnew/3.13.html:

Removed the following unittest functions, deprecated in Python 3.11:
- unittest.findTestCases()
- unittest.makeSuite()
- unittest.getTestCaseNames()


https://docs.python.org/3.13/whatsnew/3.13.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-rawhide-x86_64/07335242-python-cclib/

For all our attempts to build python-cclib with Python 3.13, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/python-cclib/

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.13:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/

Let us know here if you have any questions.

Python 3.13 is planned to be included in Fedora 41.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.13.
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.


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