gh-136535: Tests: Correct Py_TPFLAGS_MANAGED_DICT in test_class.py#136538
gh-136535: Tests: Correct Py_TPFLAGS_MANAGED_DICT in test_class.py#136538corona10 merged 5 commits into
Py_TPFLAGS_MANAGED_DICT in test_class.py#136538Conversation
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
Sorry, something went wrong.
665ca05 to
6050223
Compare
July 11, 2025 14:22
…ass.py` The `Py_TPFLAGS_MANAGED_DICT` constant in `Lib/test/test_class.py` was incorrectly set to (1 << 2) instead of the correct (1 << 4) from object.h.
30edb78 to
407de3c
Compare
July 12, 2025 11:54
There was a problem hiding this comment.
LGTM, I also double checked with the original reference:
Line 551 in 47b01da
I am waiting @Fidget-Spinner or @markshannon 's review also.
Sorry, something went wrong.
corona10
left a comment
There was a problem hiding this comment.
Hi would you like to improve the test if the is Py_TPFLAGS_MANAGED_DICT wrongly set?
With my local change it is passed if I modify the value into 1 << 2, I prefer to prevent regression in the future.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
Hello. I thought the test I added would prevent regression issues, but it didn't. |
Sorry, something went wrong.
corona10
left a comment
There was a problem hiding this comment.
lgtm!
Sorry, something went wrong.
This reverts commit b39ca1a.
|
Is there any feedback or are there any requested changes I should be aware of? |
Sorry, something went wrong.
|
I completely forgot how the managed dict works as it's been a few years, so I don't think I can review this. Sorry! |
Sorry, something went wrong.
aa4b5a7
into
python:main
Oct 24, 2025
…ass.py` (pythongh-136538) (cherry picked from commit aa4b5a7) Co-authored-by: Jiseok CHOI <jiseok.dev@gmail.com>
…ass.py` (pythongh-136538) (cherry picked from commit aa4b5a7) Co-authored-by: Jiseok CHOI <jiseok.dev@gmail.com>
⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️Hi! The buildbot AMD64 Windows11 Bigmem 3.14 (tier-1) has failed when building commit 08f6b3f. What do you need to do:
You can take a look at the buildbot page here: https://buildbot.python.org/#/builders/1799/builds/435 Failed tests:
Failed subtests:
Summary of the results of the build (if available): == Click to see traceback logsTraceback (most recent call last):
File "R:\buildarea\3.14.ambv-bb-win11.bigmem\build\Lib\test\test_os.py", line 3014, in test_listmounts
self.assertSetEqual(
~~~~~~~~~~~~~~~~~~~^
set(mounts),
^^^^^^^^^^^^
self.known_mounts & set(mounts),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
AssertionError: Items in the first set but not the second:
'R:\\'
|
Sorry, something went wrong.
The
Py_TPFLAGS_MANAGED_DICTconstant inLib/test/test_class.pywas incorrectly set to (1 << 2) instead of the correct (1 << 4) from object.h.issue: #136535
Py_TPFLAGS_MANAGED_DICTinLib/test/test_class.py#136535