Bug 2155445 - python-pycryptodomex fails to build with Python 3.12: AttributeError: 'TestEccPoint_Ed25519' object has no attribute 'failUnless'
Summary: python-pycryptodomex fails to build with Python 3.12: AttributeError: 'TestEc...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pycryptodomex
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohamed El Morabity
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PYTHON3.12
TreeView+ depends on / blocked
 
Reported: 2022-12-21 09:35 UTC by Tomáš Hrnčiar
Modified: 2023-01-08 13:01 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-01-08 13:01:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomáš Hrnčiar 2022-12-21 09:35:14 UTC
python-pycryptodomex fails to build with Python 3.12.0a3.

======================================================================
ERROR: test_negate (Cryptodome.SelfTest.PublicKey.test_ECC_25519.TestEccPoint_Ed25519.test_negate)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/pycryptodome-3.15.0/build/lib.linux-x86_64-cpython-312/Cryptodome/SelfTest/PublicKey/test_ECC_25519.py", line 114, in test_negate
    self.failUnless(sum.is_point_at_infinity())
    ^^^^^^^^^^^^^^^
AttributeError: 'TestEccPoint_Ed25519' object has no attribute 'failUnless'

======================================================================
ERROR: test_pai (Cryptodome.SelfTest.PublicKey.test_ECC_25519.TestEccPoint_Ed25519.test_pai)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/pycryptodome-3.15.0/build/lib.linux-x86_64-cpython-312/Cryptodome/SelfTest/PublicKey/test_ECC_25519.py", line 108, in test_pai
    self.failUnless(pai.is_point_at_infinity())
    ^^^^^^^^^^^^^^^
AttributeError: 'TestEccPoint_Ed25519' object has no attribute 'failUnless'

======================================================================
ERROR: test_negate (Cryptodome.SelfTest.PublicKey.test_ECC_448.TestEccPoint_Ed448.test_negate)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/pycryptodome-3.15.0/build/lib.linux-x86_64-cpython-312/Cryptodome/SelfTest/PublicKey/test_ECC_448.py", line 114, in test_negate
    self.failUnless(sum.is_point_at_infinity())
    ^^^^^^^^^^^^^^^
AttributeError: 'TestEccPoint_Ed448' object has no attribute 'failUnless'

======================================================================
ERROR: test_pai (Cryptodome.SelfTest.PublicKey.test_ECC_448.TestEccPoint_Ed448.test_pai)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/builddir/build/BUILD/pycryptodome-3.15.0/build/lib.linux-x86_64-cpython-312/Cryptodome/SelfTest/PublicKey/test_ECC_448.py", line 108, in test_pai
    self.failUnless(pai.is_point_at_infinity())
    ^^^^^^^^^^^^^^^
AttributeError: 'TestEccPoint_Ed448' object has no attribute 'failUnless'

Removed many old deprecated unittest features:

    - A number of TestCase method aliases:

    | Deprecated alias      |  Method Name           | Deprecated in |
    +-----------------------|------------------------|---------------+
    | failUnless            | assertTrue()           |      3.1      |
    | failIf                | assertFalse()          |      3.1      |
    | failUnlessEqual       | assertEqual()          |      3.1      |
    | failIfEqual           | assertNotEqual()       |      3.1      |
    | failUnlessAlmostEqual | assertAlmostEqual()    |      3.1      |
    | failIfAlmostEqual     | assertNotAlmostEqual() |      3.1      |
    | failUnlessRaises      | assertRaises()         |      3.1      |
    | assert_               | assertTrue()           |      3.2      |
    | assertEquals          | assertEqual()          |      3.2      |
    | assertNotEquals       | assertNotEqual()       |      3.2      |
    | assertAlmostEquals    | assertAlmostEqual()    |      3.2      |
    | assertNotAlmostEquals | assertNotAlmostEqual() |      3.2      |
    | assertRegexpMatches   | assertRegex()          |      3.2      |
    | assertRaisesRegexp    | assertRaisesRegex()    |      3.2      |
    | assertNotRegexpMatches| assertNotRegex()       |      3.5      |
    +-----------------------|------------------------|---------------+

    You can use https://github.com/isidentical/teyit to automatically modernise your unit tests.

    - Undocumented and broken TestCase method assertDictContainsSubset (deprecated in Python 3.2).

    - Undocumented TestLoader.loadTestsFromModule parameter use_load_tests (deprecated and ignored since Python 3.2).

    - An alias of the TextTestResult class: _TextTestResult (deprecated in Python
3.2).

(Contributed by Serhiy Storchaka in bpo-45162.)
https://bugs.python.org/issue?@action=redirect&bpo=45162



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

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.12/fedora-rawhide-x86_64/05129479-python-pycryptodomex/

For all our attempts to build python-pycryptodomex with Python 3.12, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.12/package/python-pycryptodomex/

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

Let us know here if you have any questions.

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