delta/cpython-git.git/Tools, branch v3.10.0a2

bpo-42218: Correctly handle errors in left-recursive rules (GH-23065)

2020-10-31T18:31:41+00:00

Left-recursive rules need to check for errors explicitly, since
even if the rule returns NULL, the parsing might continue and lead
to long-distance failures.

Co-authored-by: Pablo Galindo

bpo-36876: Small adjustments to the C-analyzer tool. (GH-23045)

2020-10-30T21:46:52+00:00

This is a little bit of clean-up, small fixes, and additional helpers prior to building an updated & accurate list of globals to eliminate.

bpo-42208: Fix test_gdb for gc_collect_main() name (GH-23041)

2020-10-30T20:09:48+00:00

The gcmodule.c collect() function was renamed to gc_collect_main():
update gdb/libpython.py (python-gdb.py).

bpo-42161: Remove private _PyLong_Zero and _PyLong_One (GH-23003)

2020-10-27T20:34:33+00:00

Use PyLong_FromLong(0) and PyLong_FromLong(1) of the public C API
instead. For Python internals, _PyLong_GetZero() and _PyLong_GetOne()
of pycore_long.h can be used.

bpo-42123: Run the parser two times and only enable invalid rules on the second run (GH-22111)

2020-10-26T22:42:04+00:00

* Implement running the parser a second time for the errors messages

The first parser run is only responsible for detecting whether
there is a `SyntaxError` or not. If there isn't the AST gets returned.
Otherwise, the parser is run a second time with all the `invalid_*`
rules enabled so that all the customized error messages get produced.

bpo-36876: Fix the C analyzer tool. (GH-22841)

2020-10-23T00:42:51+00:00

The original tool wasn't working right and it was simpler to create a new one, partially re-using some of the old code. At this point the tool runs properly on the master. (Try: ./python Tools/c-analyzer/c-analyzer.py analyze.)  It take ~40 seconds on my machine to analyze the full CPython code base.

Note that we'll need to iron out some OS-specific stuff (e.g. preprocessor). We're okay though since this tool isn't used yet in our workflow. We will also need to verify the analysis results in detail before activating the check in CI, though I'm pretty sure it's close.

https://bugs.python.org/issue36876

bpo-41971: Fix test failure in test.test_tools.test_c_analyzer when mutating global state (GH-22652)

2020-10-11T20:34:51+00:00

bpo-41985: Add _PyLong_FileDescriptor_Converter and AC converter for "fildes". (GH-22620)

2020-10-09T20:00:45+00:00

Revert "Fix all Python Cookbook links (#22205)" (GH-22424)

2020-09-27T00:47:25+00:00

This commit reverts commit ac0333e1e117b7f61ed7ef1dbcdb6e515ada603b as the original links are working again and they provide extended features such as comments and alternative versions.

bpo-41834: Remove _Py_CheckRecursionLimit variable (GH-22359)

2020-09-23T12:04:57+00:00

Remove the global _Py_CheckRecursionLimit variable: it has been
replaced by ceval.recursion_limit of the PyInterpreterState
structure.

There is no need to keep the variable for the stable ABI, since
Py_EnterRecursiveCall() and Py_LeaveRecursiveCall() were not usable
in Python 3.8 and older: these macros accessed PyThreadState members,
whereas the PyThreadState structure is opaque in the limited C API.