[issue41826] test_peg_generator compilation warnings

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue41826] test_peg_generator compilation warnings

Lysandros Nikolaou added the comment: New changeset c111355480ff51b50a671679c5099f534cb01cae by Pablo Galindo in branch 'master': bpo-41826: Fix compiler warnings in test_peg_generator (GH-22455) https://github.com/python/cpython/commit/c111355480ff51b50a671679c5099f534cb01cae -- no

[issue41826] test_peg_generator compilation warnings

Change by Pablo Galindo Salgado : -- pull_requests: +21484 pull_request: https://github.com/python/cpython/pull/22455 ___ Python tracker ___ ___

[issue41826] test_peg_generator compilation warnings

Skip Montanaro added the comment: I created a PR from my patch, but it includes all the merges to my smontanaro/cpython master branch from python/cpython. I thought I was following the instructions properly (https://devguide.python.org/gitbootcamp/#creating-a-pull-request), but I guess I'm

[issue41826] test_peg_generator compilation warnings

Change by Skip Montanaro : -- pull_requests: +21450 stage: -> patch review pull_request: https://github.com/python/cpython/pull/22412 ___ Python tracker ___ __

[issue41826] test_peg_generator compilation warnings

Skip Montanaro added the comment: Possible patch. All this does is add some C casts. @pablogsal suggested there was more to be done, but my glance at the reference he gave suggested that's already been done. My apologies if I misinterpreted his reference. -- keywords: +patch Added fi

[issue41826] test_peg_generator compilation warnings

Pablo Galindo Salgado added the comment: > I'm sorry, that doesn't mean much to me. Is it simply a matter of applying suitable casts to the various parameters in the C code fragments in those? Yep, and in the capture variables and in the rule types. Check https://github.com/python/cpython/pul

[issue41826] test_peg_generator compilation warnings

Skip Montanaro added the comment: > This is because the types of the grammars in Lib/test/test_peg_generator/test_c_parser.py needs to be updated to use the new sequences I'm sorry, that doesn't mean much to me. Is it simply a matter of applying suitable casts to the various parameters in the

[issue41826] test_peg_generator compilation warnings

Pablo Galindo Salgado added the comment: This is because the types of the grammars in Lib/test/test_peg_generator/test_c_parser.py needs to be updated to use the new sequences -- ___ Python tracker ___

[issue41826] test_peg_generator compilation warnings

Change by Karthikeyan Singaravelan : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue41826] test_peg_generator compilation warnings

New submission from Skip Montanaro : I don't see anything like this while building Python proper, but when test_peg_generator is run, it spews a few compiler warnings. Platform is Ubuntu 20.04. Seems low-ish priority, but I saw no mention of it in a quick bpo search, so thought I would toss it