On Tue, May 18, 2021 at 2:49 PM Pablo Galindo Salgado
wrote:
> * It actually doesn't have more advantages. The current solution in the PEP
> can do exactly the same as this solution if you allow reparsing when
> displaying tracebacks. This is because with the start line, end line, start
> offset
>
> Excellent point! Do you know how reliable this is in practice, i.e.
> what proportion of bytecode source spans are something you can
> successfully pass to ast.parse? If it works it's obviously nicer, but
> I can't tell how often it works. E.g. anything including
> return/break/continue/yield/a
On 5/13/2021 4:18 AM, Mark Shannon wrote:
Hi Terry,
On 13/05/2021 5:32 am, Terry Reedy wrote:
On 5/12/2021 1:40 PM, Mark Shannon wrote:
This is an informational PEP about a key part of our plan to improve
CPython performance for 3.11 and beyond.
As always, comments and suggestions are welc
The Python Developers Guide specifically states to get VS2017 for developing
or enhancing python on a Windows system.
Is it still correct to specifically use VS2017 , or is VS2019 also
acceptable?
I ask this because I know that the *.vcproj files and other
build-environment files have chang
