Skip to content

Conversation

@midnightstardust
Copy link

@midnightstardust midnightstardust commented Aug 2, 2024

Fixed an existing old issue with the whitespace by making a small change. This is my first PR to cpython so thanks for taking the time to review this and opening the issue.

@midnightstardust midnightstardust requested a review from a team as a code owner August 2, 2024 14:34
@ghost
Copy link

ghost commented Aug 2, 2024

All commit authors signed the Contributor License Agreement.
CLA signed

@bedevere-app
Copy link

bedevere-app bot commented Aug 2, 2024

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 skip news label instead.

blurb-it bot and others added 4 commits August 2, 2024 14:37
…ythonGH-122577)

The `PyStructSequence` destructor would crash if it was deallocated after
its type's dictionary was cleared by the GC, because it couldn't compute
the "real size" of the instance. This could occur with relatively
straightforward code in the free-threaded build or with a reference
cycle involving the type in the default build, due to differing orders
in which `tp_clear()` was called.

Account for the non-sequence fields in `tp_basicsize` and use that,
along with `Py_SIZE()`, to compute the "real" size of a
`PyStructSequence` in the dealloc function. This avoids the accesses to
the type's dictionary during dealloc, which were unsafe.
@@ -0,0 +1 @@
Fixed an existing issue with email header lib adding whitespace
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like how this entry is worded. How about something like this?

Suggested change
Fixed an existing issue with email header lib adding whitespace
Fixed :mod:`email` preserving leading whitespace in wrapped headers.

@ZeroIntensity
Copy link
Member

ZeroIntensity commented Aug 2, 2024

Looks like this doesn't fully fix #109252. The original reproducer still gives the same error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants