[Python-Dev] Re: [python-committers] Roundup to GitHub Issues migration

2021-08-05 Thread Victor Stinner 
Hi Ezio,

What is the status of the migration of Python issues from
bugs.python.org (Roundup) to GitHub? Is it still a work-in-progress or
is it stalled?

Victor

On Mon, Jun 21, 2021 at 4:20 AM Ezio Melotti  wrote:
>
> As you might know, PEP 581 (Using GitHub Issues for CPython) has been
> approved.  I've been working with Ewa, Ee, the Working Group, the
> Steering Council, and the GitHub folks to make this happen, and the SC
> encouraged me to give you all a quick update.
>
> This effort is being tracked at
> : this board reflects
> the current status of the project.  The PEPs (including PEP 588 --
> GitHub Issues Migration Plan) haven't been updated yet and might
> contain outdated information, so please refer to the psf/gh-migration
> repo for the latest updates.
>
> During the next phase I will work with the WG to sort out all the
> major issues that we might encounter, and then I will once again reach
> out to you to gather feedback from the wider audience that follows
> these mailing lists.
>
> Best Regards,
> Ezio Melotti
> ___
> python-committers mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/[email protected]/message/QQT7DOKTBKZRFLT6GUJLNQOC3YDLBSLU/
> Code of Conduct: https://www.python.org/psf/codeofconduct/



-- 
Night gathers, and now my watch begins. It shall not end until my death.
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/MLP7A3SSX5G6GMILAKEWWK5TGRA7AK54/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Devguide document on PEG parser

2021-08-05 Thread Eric V. Smith 
I’ve only just started to read this, but thanks so much for writing it, Pablo. 
It will be a great help.

--
Eric

> On Aug 4, 2021, at 5:05 PM, Pablo Galindo Salgado  wrote:
> 
> 
> Hi,
> 
> After some effort, I just finished a new extensive document in the devguide 
> regarding how
> to use the new PEG parser and the PEG grammar:
> 
> https://devguide.python.org/parser/
> 
> The document contains descriptions, backgrounds, references, guides, and 
> tips. Ideally,
> this will make it a bit easier for everyone that wants to deal with the 
> grammar or the parser.
> 
> Hope that you find it useful :)
> 
> P.S. Thanks to everyone that helped with the review!
> 
> Regards from cloudy London,
> Pablo Galindo Salgado
> ___
> Python-Dev mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at 
> https://mail.python.org/archives/list/[email protected]/message/WNPUUAPUZEQ6UY3DEJE2JAYT2FZZXWE3/
> Code of Conduct: http://python.org/psf/codeofconduct/
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/5CAQ6SX354SYP2QLWKXG6TYSMA4XQZ7I/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PEP 467 feedback from the Steering Council

2021-08-05 Thread Stephen J. Turnbull 
Christopher Barker writes:

 > A byte is not a character

While I am -0.5 on bchr for many of the reasons already cited in the
thread (and would be -1 if the methods names proposed for the feature
were a bit more aesthetic), I don't think this argument is valid.
Bytes that could otherwise be arbitrary (aka "magic numbers") are
*often* chosen because they correspond to the ASCII repertoire.  And
strings is still a useful utility for C programmers, even if not so
much for others.

It's true that bytes are still bytes, characters are still characters,
and it's a very good thing from my point of view that Python 3 gave us
a consistent separation -- the only thing I ever explicitly use bytes
for is passwords for zipfiles, and the implicit handling of bytes
ontherwise just works for me :-).  But it turns out it was a mistake
to make it so hard for consenting adults to treat bytes as characters
in certain contexts (for example, PEP 461 -- note: I opposed that PEP
and I was wrong -- should have been part of Python 3.0).

Steve
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/ZASN3G7VZBZSAYY6CH5GUDDENOZ6NJKR/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PEP 467 feedback from the Steering Council

2021-08-05 Thread Antoine Pitrou 
On Fri, 6 Aug 2021 01:37:48 +0900
"Stephen J. Turnbull"  wrote:
> Christopher Barker writes:
> 
>  > A byte is not a character  
> 
> While I am -0.5 on bchr for many of the reasons already cited in the
> thread (and would be -1 if the methods names proposed for the feature
> were a bit more aesthetic), I don't think this argument is valid.
> Bytes that could otherwise be arbitrary (aka "magic numbers") are
> *often* chosen because they correspond to the ASCII repertoire.  And
> strings is still a useful utility for C programmers, even if not so
> much for others.

In what context is `bchr()` useful?

Regards

Antoine.


___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/MLJRB4YJBSWPCC75UVFHHXDKMOQVEMZT/
Code of Conduct: http://python.org/psf/codeofconduct/