This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients cheryl.sabella, terry.reedy
Date 2018-02-20.02:19:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1519093154.93.0.467229070634.issue32880@psf.upfronthosting.co.za>
In-reply-to
Content
Pyparse was mostly written in the early 2000s, with the only one code change since 2007 in 2014. #32874 will add tests for pyparse 'as is' (though with some docstring and comment changes).  This issue will change pyparse code, and change or add test as needed.

Here are two items to fix.  More will be added.  Some fixes might be separate PRs or spun off into separate issues.

def dump: dump this; print does the same, without hardcoding sys.__stdout__, which might be None.

_synchre: Only used in find_good_parse_start. Missing 'if' (mentioned in function docstring as 'popular' and 'for' and new things like 'with'. 'async' and 'await' are not generally popular, but is not any statement beginning a good parse start?
History
Date User Action Args
2018-02-20 02:19:14terry.reedysetrecipients: + terry.reedy, cheryl.sabella
2018-02-20 02:19:14terry.reedysetmessageid: <1519093154.93.0.467229070634.issue32880@psf.upfronthosting.co.za>
2018-02-20 02:19:14terry.reedylinkissue32880 messages
2018-02-20 02:19:14terry.reedycreate