Skip to content

DOC: Clarify version number in logging.rst #136585

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Conversation

wjandrea
Copy link
Contributor

@wjandrea wjandrea commented Jul 12, 2025

3.4 technically includes 3.4.2, so put 3.4.0 to clarify.


📚 Documentation preview 📚: https://cpython-previews--136585.org.readthedocs.build/

wjandrea added 2 commits July 12, 2025 11:08
Fix typo: "due to retain" → "in order to retain"

"in order" is grammatically redundant, but it's to avoid having homophones "2" and "to" right next to each other.
3.4 technically includes 3.4.2, so put 3.4.0 to clarify.
@wjandrea wjandrea requested a review from vsajip as a code owner July 12, 2025 14:15
@python-cla-bot
Copy link

python-cla-bot bot commented Jul 12, 2025

All commit authors signed the Contributor License Agreement.

CLA signed

@StanFromIreland
Copy link
Member

StanFromIreland commented Jul 12, 2025

I don't think 2 PRs are nesecarry for such a small section.

Ps. You need to sign the CLA

text level, and would return the corresponding numeric value of the level.
This undocumented behaviour was considered a mistake, and was removed in
Python 3.4, but reinstated in 3.4.2 due to retain backward compatibility.
Python 3.4.0, but reinstated in 3.4.2 in order to retain backward compatibility.
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this duplicate to #136584 ? We actually treat them separately.

Suggested change
Python 3.4.0, but reinstated in 3.4.2 in order to retain backward compatibility.
Python 3.4.0, but reinstated in 3.4.2 due to retain backward compatibility.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry, what do you mean by "separately"?

@wjandrea
Copy link
Contributor Author

Ps. You need to sign the CLA

I have signed the agreement, years ago, just not under this GitHub email address.

@StanFromIreland
Copy link
Member

Then you must also add your gh address.

@picnixz
Copy link
Member

picnixz commented Jul 13, 2025

I don't think it's necessary. Python 3.4 is really EOL and IMO it's sufficiently clear considering the rest of the paragraph. We also don't have a policy of mentioning the minor version in such notes (I think we should even remove the mention to 3.4.2 now because it's really something that is not useful to the user reading the online notes). I'm going to reject this one.

@picnixz picnixz closed this Jul 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

5 participants