Skip to content
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

gh-93626: Set the release for __future__.annotations to None #93628

Merged
merged 3 commits into from Jul 5, 2022

Conversation

KotlinIsland
Copy link
Contributor

@KotlinIsland KotlinIsland commented Jun 9, 2022

Hi everyone, I noticed that __future__.annotations was turned on in the 3.11 betas 😳😳😳😳😳😳.

This is highly sus as it should be turned off till further notice (3.12 :trollface:) (None kinda means 'tbd' I think).

This is my first cpython contrib, I tried to follow the contributing process, but maybe I missed something, sorry!

This PR also needs to be backported to the 3.11 branch

resolves: #93626

Corresponding typeshed PR python/typeshed#8232

@cpython-cla-bot
Copy link

cpython-cla-bot bot commented Jun 9, 2022

All commit authors signed the Contributor License Agreement.
CLA signed

@KotlinIsland
Copy link
Contributor Author

KotlinIsland commented Jun 9, 2022

I think your CLA facility is busted, when I sign it, it just says:

Thank you for authorizing our application, but the CLA must be signed by the users who contributed to the PR. Authors emails are: kotlinisland@users.noreply.github.com.

@Fidget-Spinner Fidget-Spinner requested a review from pablogsal Jun 9, 2022
@KotlinIsland
Copy link
Contributor Author

KotlinIsland commented Jun 19, 2022

@pablogsal I've changed the mandatory release to None to reflect that the release version is 'tbd'

@ambv
Copy link
Contributor

ambv commented Jun 20, 2022

@KotlinIsland can you try signing the CLA again?

@KotlinIsland
Copy link
Contributor Author

KotlinIsland commented Jun 20, 2022

@ambv

Thank you for authorizing our application, but the CLA must be signed by the users who contributed to the PR. Authors emails are: kotlinisland@users.noreply.github.com,65446343+KotlinIsland@users.noreply.github.com.

@ambv
Copy link
Contributor

ambv commented Jun 20, 2022

@KotlinIsland please try again.

@KotlinIsland KotlinIsland changed the title gh-93626: Set the release for __future__.annotations to 3.12 gh-93626: Set the release for __future__.annotations to None Jun 21, 2022
@KotlinIsland
Copy link
Contributor Author

KotlinIsland commented Jun 21, 2022

@ambv it worked 😳.
Thanks 😁

@KotlinIsland
Copy link
Contributor Author

KotlinIsland commented Jun 29, 2022

@graingert This needs to be backported to 3.11

@KotlinIsland
Copy link
Contributor Author

KotlinIsland commented Jun 29, 2022

@pablogsal This is a critical release blocker for 3.11

Copy link

@DetachHead DetachHead left a comment

LGTM 🚀🚀🚀

@@ -377,6 +377,10 @@ Other Language Changes
coerces negative zero to zero after rounding to the format precision. See
:pep:`682` for more details. (Contributed by John Belmonte in :gh:`90153`.)

* :pep:`563` Postponed Evaluation of Annotations, ``__future__.annotations`` has been indefinitely postponed.
Copy link
Member

@JelleZijlstra JelleZijlstra Jun 29, 2022

Choose a reason for hiding this comment

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

I don't think this fits here as there's no change.

Copy link
Contributor Author

@KotlinIsland KotlinIsland Jun 30, 2022

Choose a reason for hiding this comment

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

Personally I rushed to the release page to see the status of pep 563 as in 3.10 it was marked as being released in 3.11. And was surprised to see that there was no mention of it, despite the fact that it has been pulled from 3.11.

I hadn't seen any of the information regarding it's changed status, it would be of value to be to have it in here. Maybe it could be moved to a different section of the release notes? or maybe the full-form changelog?

Copy link
Contributor Author

@KotlinIsland KotlinIsland Jun 30, 2022

Choose a reason for hiding this comment

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

Perhaps in the "Improved Modules" section it could be listed under __future__?

Copy link
Member

@zware zware Jun 30, 2022

Choose a reason for hiding this comment

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

I would suggest something along the lines of a "Non-futures Related to Type Hints" subsection of the "New Features Related to Type Hints" section above. Maybe not that particular name, but I enjoyed coming up with it :)

Lines in our reST docs should be wrapped at 80 columns as noted in the devguide.

Copy link
Contributor Author

@KotlinIsland KotlinIsland Jul 1, 2022

Choose a reason for hiding this comment

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

Done, I used your suggested name because I didn't understand what you meant by it😁

zware
zware previously requested changes Jun 30, 2022
@@ -377,6 +377,10 @@ Other Language Changes
coerces negative zero to zero after rounding to the format precision. See
:pep:`682` for more details. (Contributed by John Belmonte in :gh:`90153`.)

* :pep:`563` Postponed Evaluation of Annotations, ``__future__.annotations`` has been indefinitely postponed.
Copy link
Member

@zware zware Jun 30, 2022

Choose a reason for hiding this comment

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

I would suggest something along the lines of a "Non-futures Related to Type Hints" subsection of the "New Features Related to Type Hints" section above. Maybe not that particular name, but I enjoyed coming up with it :)

Lines in our reST docs should be wrapped at 80 columns as noted in the devguide.

Lib/__future__.py Show resolved Hide resolved
@bedevere-bot
Copy link

bedevere-bot commented Jun 30, 2022

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 I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

Lib/__future__.py Outdated Show resolved Hide resolved
Copy link
Member

@gvanrossum gvanrossum left a comment

Two nits (tweaking the section heading, and keeping the long url on one line), otherwise LGTM.

Doc/whatsnew/3.11.rst Outdated Show resolved Hide resolved
Doc/whatsnew/3.11.rst Outdated Show resolved Hide resolved
@zware zware dismissed their stale review Jul 5, 2022

Changes made, chance to re-review not currently available

KotlinIsland and others added 2 commits Jul 5, 2022
Co-authored-by: Guido van Rossum <gvanrossum@gmail.com>
Co-authored-by: Guido van Rossum <gvanrossum@gmail.com>
@ambv ambv merged commit 4791a8a into python:main Jul 5, 2022
14 checks passed
@miss-islington
Copy link
Contributor

miss-islington commented Jul 5, 2022

Thanks @KotlinIsland for the PR, and @ambv for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11.
🐍🍒⛄1�7🤖

@bedevere-bot
Copy link

bedevere-bot commented Jul 5, 2022

GH-94553 is a backport of this pull request to the 3.11 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jul 5, 2022
pythonGH-93628)

Co-authored-by: Guido van Rossum <gvanrossum@gmail.com>
(cherry picked from commit 4791a8a)

Co-authored-by: KotlinIsland <65446343+KotlinIsland@users.noreply.github.com>
@graingert
Copy link
Contributor

graingert commented Jul 5, 2022

does this make sense backported to 3.10?

@ambv
Copy link
Contributor

ambv commented Jul 5, 2022

There is no 3.11 whatsnew in 3.10 and it seems to me that the clarified meaning of None shouldn't be used mid-release cycle.

ambv pushed a commit that referenced this pull request Jul 5, 2022
 1�793628) (GH-94553)

Co-authored-by: Guido van Rossum <gvanrossum@gmail.com>
(cherry picked from commit 4791a8a)

Co-authored-by: KotlinIsland <65446343+KotlinIsland@users.noreply.github.com>
@KotlinIsland KotlinIsland deleted the patch-1 branch Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

__future__.annotations has inaccurate mandatoryRelease value
9 participants