Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[3.13] gh-135307: Fix email error when policy max_line_length is set to 0 or None (GH-135367)#140917

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
bitdancer merged 2 commits intopython:3.13fromzangjiucheng:backport-6d45cd8-3.13
Nov 2, 2025

Conversation

@zangjiucheng
Copy link
Contributor

@zangjiuchengzangjiucheng commentedNov 2, 2025
edited by bedevere-appbot
Loading

(cherry picked from commit6d45cd8)

RDM: Like the change made in a earlier PR to the folder, we can/must use 'maxlen' as a stand in for 'unlimited' when computing line lengths when max_line_length is 0 or None; otherwise the computation results in a traceback.

…s set to 0 or None (pythonGH-135367)(cherry picked from commit6d45cd8)Co-authored-by: Jiucheng(Oliver) <git.jiucheng@gmail.com>RDM: Like the change made in a earlier PR to the folder, we can/must use 'maxlen' as a stand in for 'unlimited' when computing line lengths when max_line_length is 0 or None; otherwise the computation results in a traceback.
parsed_body=parsed.get_body().get_content().rstrip('\n')
self.assertEqual(parsed_body,body)

deftest_invalid_header_names(self):
Copy link
Member

Choose a reason for hiding this comment

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

These invalid header name tests are the conflict that caused the automatic back port to fail. You'll need to delete them (they are tests for a change that was not back ported from 3.14 to 3.13). (cherry-picker conflicts can be quite confusing).

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I see, thanks. I am going to address that.

@bitdancerbitdancer merged commit10af840 intopython:3.13Nov 2, 2025
41 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@bitdancerbitdancerbitdancer left review comments

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@zangjiucheng@bitdancer

[8]ページ先頭

©2009-2025 Movatter.jp