Bug 2275047 - python-zope-interface fails with Python 3.13: zope.interface.exceptions.InvalidInterface: Concrete attribute, __static_attributes__
Summary: python-zope-interface fails with Python 3.13: zope.interface.exceptions.Inval...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-zope-interface
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lumír Balhar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.13
TreeView+ depends on / blocked
 
Reported: 2024-04-15 06:46 UTC by Karolina Surma
Modified: 2024-04-15 11:33 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-04-15 11:33:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karolina Surma 2024-04-15 06:46:42 UTC
python-zope-i18nmessageid fails to build with Python 3.13.0a6.

+ /usr/bin/python3 -m tox --current-env -q --recreate -e py313
Traceback (most recent call last):
  File "/usr/bin/zope-testrunner", line 8, in <module>
    sys.exit(run())
             ~~~^^
  File "/usr/lib/python3.13/site-packages/zope/testrunner/__init__.py", line 31, in run
    failed = run_internal(defaults, args, script_parts=script_parts, cwd=cwd,
             ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                          warnings=warnings)
                          ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/zope/testrunner/__init__.py", line 52, in run_internal
    from zope.testrunner.runner import Runner
  File "/usr/lib/python3.13/site-packages/zope/testrunner/runner.py", line 35, in <module>
    import zope.testrunner._doctest
  File "/usr/lib/python3.13/site-packages/zope/testrunner/_doctest.py", line 20, in <module>
    import zope.testrunner.feature
  File "/usr/lib/python3.13/site-packages/zope/testrunner/feature.py", line 19, in <module>
    import zope.testrunner.interfaces
  File "/usr/lib/python3.13/site-packages/zope/testrunner/interfaces.py", line 32, in <module>
    class IFeature(zope.interface.Interface):
    ...<57 lines>...
            """
  File "/usr/lib64/python3.13/site-packages/zope/interface/interface.py", line 774, in __init__
    self.__attrs = self.__compute_attrs(attrs)
                   ~~~~~~~~~~~~~~~~~~~~^^^^^^^
  File "/usr/lib64/python3.13/site-packages/zope/interface/interface.py", line 793, in __compute_attrs
    aname: update_value(aname, aval)
           ~~~~~~~~~~~~^^^^^^^^^^^^^
  File "/usr/lib64/python3.13/site-packages/zope/interface/interface.py", line 789, in update_value
    raise InvalidInterface("Concrete attribute, " + aname)
zope.interface.exceptions.InvalidInterface: Concrete attribute, __static_attributes__
py313: exit 1 (0.08 seconds) /builddir/build/BUILD/zope.i18nmessageid-6.1.0> zope-testrunner --test-path=src -vc pid=329
  py313: FAIL code 1 (0.09 seconds)

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/07303001-python-zope-i18nmessageid/

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

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.