[Python-Dev] Re: Please be careful about changing PEPs post-submission to the SC

2021-11-18 Thread Kyle Stanley
FWIW that seems like a reasonable approach, at least to me. On Thu, Nov 18, 2021, 5:29 PM Guido van Rossum wrote: > I know PEP 646 was one of these. In our defense, we *did* notify the SC > that there was a pending issue ( > https://github.com/python/steering-council/issues/59#issuecomment-95172

[Python-Dev] Re: Please be careful about changing PEPs post-submission to the SC

2021-11-18 Thread Guido van Rossum
I know PEP 646 was one of these. In our defense, we *did* notify the SC that there was a pending issue ( https://github.com/python/steering-council/issues/59#issuecomment-951728233), although at the time we didn't anticipate it to become such a contentious discussion between the PEP authors. (Thoug

[Python-Dev] Re: SC Acceptance: PEP 646 -- Variadic Generics

2021-11-18 Thread Matthew Rahtz via Python-Dev
Hi Barry, Absolutely fantastic - thank you for letting us know! As Guido says, there's one final thing that we thought would be easy to resolve but has actually turned out to be a little tricky. Happy to proceed as you think is best here. Matthew On Wed, 17 Nov 2021 at 22:33, Guido van Rossum w

[Python-Dev] Please be careful about changing PEPs post-submission to the SC

2021-11-18 Thread Brett Cannon
This is a personal plea (i.e. not coming from the SC at all), but in the last month we have had PEPs changed twice post-submission to the SC. That's a big time sink as we take multiple meetings to discuss a PEP and having things change underneath us causes us to have to re-evaluate our discussions

[Python-Dev] Re: SC Acceptance: PEP 646 -- Variadic Generics

2021-11-18 Thread Brett Cannon
I put the PEP back on our agenda to discuss this. On Wed, Nov 17, 2021 at 2:40 PM Guido van Rossum wrote: > Hi Barry, > > That's fantastic news! > > Somewhat embarrassingly, on typing-sig we're still discussing one or two > final tweaks. In particular, the PEP as accepted forbids a certain > con

[Python-Dev] Re: Do we need to remove everything that's deprecated?

2021-11-18 Thread Petr Viktorin
On Wed, Nov 17, 2021 at 12:49 AM Terry Reedy wrote: > > On 11/16/2021 7:43 AM, Petr Viktorin wrote: > > On 16. 11. 21 1:11, Brett Cannon wrote: > > >> I think the key point with that approach is if you wanted to maximize > >> your support across supported versions, this would mean there wouldn't >

[Python-Dev] Re: Do we need to remove everything that's deprecated?

2021-11-18 Thread Petr Viktorin
On 16. 11. 21 20:13, Brett Cannon wrote: On Tue, Nov 16, 2021 at 4:46 AM Petr Viktorin > wrote: On 16. 11. 21 1:11, Brett Cannon wrote: > > > On Sun, Nov 14, 2021 at 3:01 PM Victor Stinner mailto:vstin...@python.org> >

[Python-Dev] Re: Do we need to remove everything that's deprecated?

2021-11-18 Thread Victor Stinner
Maybe once a function is deprecated in Python, pyupgrade should be updated? I mean, more collaboration between Python core devs and the pyupgrade development. https://github.com/asottile/pyupgrade Victor On Thu, Nov 18, 2021 at 8:39 AM Jeremiah Paige wrote: > > I’ve seen a few people in this th

[Python-Dev] Re: Preventing Unicode-related gotchas (Was: pre-PEP: Unicode Security Considerations for Python)

2021-11-18 Thread Eryk Sun
On 11/13/21, Terry Reedy wrote: > On 11/13/2021 4:35 PM, pt...@austin.rr.com wrote: >> >> _π“Ÿβ…¬π– π™²π—˜β„‹π’ͺLᴰ𝑬𝕽﹏𝕷𝔼𝗑 = 12 >> >> def _𝔰ʰ𝓸ʳπ•₯π™šπ‘›(𝔰, pπ‘Ÿπ”’ο¬π–π•πšŽπ‘›, sᡀ𝑓𝗳𝗂π‘₯π—Ήβ‚‘πš—): >> >> ˒𝗸i𝗽 = π₯ο½…π˜―(π–˜) - prπšŽπ–‹π’x𝗅ᡉ𝓷 - 𝒔π™ͺο¬€ο½‰π˜…π—Ήπ™šβ‚™ >> >> if ski𝘱 > _ππ—Ÿπ– π˜Šπ™΄Hπ•ΊοΌ¬π•―π™€π˜™οΉLπ”ˆπ’©: >> >> 𝘴 = '%s[%d chars]%s' % (𝙨[:π˜±π«π•–π‘“π•šο½˜β„“π’†π•Ÿ], β‚›πš”π’Šp, 𝓼[𝓁𝒆