Based on the upload of mercurial to noble-proposed unapproved, this bug
is intended to cover _all_ bad Mercurial interactions with Python 3.12,
is it? Should it be renamed?

FTR, I found the change to tests/test-profile.t alarming at first, but
then I followed the trail to
https://github.com/python/cpython/issues/110770, which says that the
feature (nested profiling?) never worked, but 3.12 now properly reports
that as an error. So this isn't hiding a real problem in Mercurial -
rather the test is wrong.

** Bug watch added: github.com/python/cpython/issues #110770
   https://github.com/python/cpython/issues/110770

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076152

Title:
  SRU: add threading to the list of modules which cannot be lazy
  imported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/2076152/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to