PSA: Please try the new pycparser 3.00 release

[eliben]

This release includes a major refactoring (removing the PLY dependency), which should cause no functional change - the emitted AST is identical and the giant test suite keeps passing.

Please try it and open issue for any problems discovered!

[sdbbs]

I guess there is not much you can do about this, but just FYI: recently I had to update Python, which also updated this package to 3.0, and I noticed that the removing of the PLY dependency breaks my usage of pycparserext - see ModuleNotFoundError: No module named 'pycparser.plyparser' · Issue #99 · inducer/pycparserext.

I would have even tried to hack some changes myself in order to make it work, and it seems I'd mostly have to get rid of the @parameterized decorator - but all I can find is that the last mentions of @parameterized were removed in commit 58a302b and unfortunately, I cannot easily see in that commit what the alternative to the use of @parameterized would be.

[eliben]

@sdbbs opening the issue for pycparserext is the right approach here. pycparserext can either lock its dependency of pycparser on an older version, or upgrade and remove the reliance on PLY as well.