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

Please formally reject PEP-536 #209

Closed
ericvsmith opened this issue Oct 9, 2023 · 7 comments · Fixed by python/peps#3510
Closed

Please formally reject PEP-536 #209

ericvsmith opened this issue Oct 9, 2023 · 7 comments · Fixed by python/peps#3510

Comments

@ericvsmith
Copy link
Member

This PEP suggested moving f-strings to the python grammar. It's basically what was implemented by PEP 701 – "Syntactic formalization of f-strings". As such, 536 is obsolete.

I was going to mark 536 as rejected, but I think there should be formal SC action to reject it, not some random committer rejecting it.

I'll do the actual work of updating the PEP, unless you want to.

Thanks.

@merwok
Copy link
Member

merwok commented Oct 24, 2023

Alternatively, the author @flying-sheep could withdraw it.

@flying-sheep
Copy link

How do I do that?

@merwok
Copy link
Member

merwok commented Oct 24, 2023

With a PR to change the status (and maybe a post on python-dev to let people know and have a link for the resolution header)

Not much info in the meta-PEP: https://peps.python.org/pep-0001/#pep-review-resolution

@flying-sheep
Copy link

flying-sheep commented Oct 24, 2023

I can just link here I guess. I agree with @ericvsmith that 701 does exactly what I intended to change with 536 (only a few years later), so I wish to widthdraw PEP 536.

@merwok
Copy link
Member

merwok commented Oct 24, 2023

I do believe it should be a link to a mailing list post (nowadays discuss).

@flying-sheep
Copy link

flying-sheep commented Oct 24, 2023

Ugh, yeah it does need to be that. CI complains otherwise.

@hugovk
Copy link
Member

hugovk commented Oct 26, 2023

PEP 536 has been withdrawn, this issue can be closed:

Thanks all.

@Yhg1s Yhg1s closed this as completed Oct 26, 2023
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 a pull request may close this issue.

5 participants