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

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 ( >

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

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.

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

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

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

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

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 >

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

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?

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?

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

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

On 11/13/21, Terry Reedy wrote: > On 11/13/2021 4:35 PM, pt...@austin.rr.com wrote: >> >> _퓟Ⅼ햠홲험ℋ풪Lᴰ푬핽﹏핷피헡 = 12 >> >> def _픰ʰ퓸ʳ핥홚푛(픰, p푟픢fi햝핝횎푛, ｓᵤ푓헳헂푥헹ₑ횗): >> >> ˢ헸ｉ헽 = 퐥ｅ혯(햘) - ｐr횎햋퐢x헅ᵉ퓷 - 풔홪ffｉ혅헹홚ₙ >> >> if sｋi혱 > _퐏헟햠혊홴H핺Ｌ핯홀혙﹏L픈풩: >> >> 혴 = '%s[%d chars]%s' % (홨[:혱퐫핖푓핚ｘℓ풆핟], ₛ횔풊p,