python-msal fails to build with Python 3.14.0a1.
=================================== FAILURES ===================================
_ TestAuthCodeReceiver.test_no_two_concurrent_receivers_can_listen_on_same_port _
self = <tests.test_authcode.TestAuthCodeReceiver testMethod=test_no_two_concurrent_receivers_can_listen_on_same_port>
def test_no_two_concurrent_receivers_can_listen_on_same_port(self):
with AuthCodeReceiver() as receiver:
expected_error = OSError if sys.version_info[0] > 2 else socket.error
> with self.assertRaises(expected_error):
E AssertionError: OSError not raised
tests/test_authcode.py:24: AssertionError
=========================== short test summary info ============================
FAILED tests/test_authcode.py::TestAuthCodeReceiver::test_no_two_concurrent_receivers_can_listen_on_same_port
https://docs.python.org/3.14/whatsnew/3.14.html
For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-rawhide-x86_64/08198524-python-msal/
For all our attempts to build python-msal with Python 3.14, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-msal/
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.14:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/
Let us know here if you have any questions.
Python 3.14 is planned to be included in Fedora 43.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.14.
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.
(In reply to Ben Beasley from comment #4)
> I just asked for status in https://github.com/python/cpython/issues/127319,
> which has had no activity since November.
I submitted https://github.com/python/cpython/pull/135405 in case they're inclined to merge what amounts to a revert. Reading through the original issue that led to the behavior change makes me think it wasn't intentional, since it makes no mention of beginning to allow port re-use.
python-msal fails to build with Python 3.14.0a1. =================================== FAILURES =================================== _ TestAuthCodeReceiver.test_no_two_concurrent_receivers_can_listen_on_same_port _ self = <tests.test_authcode.TestAuthCodeReceiver testMethod=test_no_two_concurrent_receivers_can_listen_on_same_port> def test_no_two_concurrent_receivers_can_listen_on_same_port(self): with AuthCodeReceiver() as receiver: expected_error = OSError if sys.version_info[0] > 2 else socket.error > with self.assertRaises(expected_error): E AssertionError: OSError not raised tests/test_authcode.py:24: AssertionError =========================== short test summary info ============================ FAILED tests/test_authcode.py::TestAuthCodeReceiver::test_no_two_concurrent_receivers_can_listen_on_same_port https://docs.python.org/3.14/whatsnew/3.14.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-rawhide-x86_64/08198524-python-msal/ For all our attempts to build python-msal with Python 3.14, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-msal/ 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.14: https://copr.fedorainfracloud.org/coprs/g/python/python3.14/ Let us know here if you have any questions. Python 3.14 is planned to be included in Fedora 43. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.14. 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.