-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
bpo-40636: Documentation for zip-strict #20961
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
Conversation
709b0b4
to
8dc14f5
Compare
Please ignore the docs CI failure here, it's because the feature is implemented in a separate PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this first draft! I ran out of time to review the three big bullets more carefully, but I have saved up some feedback that I hope you will take into account.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I left some comments too.
10cc1c6
to
06408a4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, after you apply Guido's feedback. Just one more tiny thing I noticed (not a big deal):
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I'll merge next. Thanks for doing this extensive update!
Hm, I can't merge because of the failing test. @cool-RR can you merge the latest master now that the implementation has been merged? |
Thanks @cool-RR! |
Co-authored-by: Brandt Bucher <brandtbucher@gmail.com>
f21ad5b
to
a67f52a
Compare
Rebased and pushed, let's see whether tests pass. I haven't squashed the commits, I assume the GitHub interface lets you do that. If you want me to squash, let me know. |
@gvanrossum: Please replace |
Congrats, and thanks! Looking forward to more of your work. |
😊 Do you want a PR to the Python 3.10 release schedule? |
Sure, can you think of other PEPs that should go in there?
On Fri, Jun 19, 2020 at 13:43 Ram Rachum ***@***.***> wrote:
😊
Do you want a PR to the Python 3.10 release schedule?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20961 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWCWMUUPOI7MQIBMFEYU4DRXPEXDANCNFSM4OBQAUVA>
.
--
--Guido (mobile)
|
I checked for PEPs with the string "Python-Version: 3.10" and besides 618, there isn't a single one that has "Status: Accepted", so I guess not. |
@brandtbucher @vstinner @gvanrossum
This is the documentation for the zip-strict feature implemented in #20921 .
When reviewing this PR, I suggest that you look at it in the HTML view.
Also, can someone put the skip-news tag here? There's a news item in the other PR.
https://bugs.python.org/issue40636