René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[MNT]: Upcoming version of `pyparsing` will start emitting `DeprecationWarnings` for legacy pre-PEP8 method and argument names","articleBody":"### Summary\n\nI'm about to release version 3.2.2 of pyparsing, which will be the last version to quietly accept both PEP8 and non-PEP8 method and argument names (for instance, accepting `parseString` as an alias for `parse_string`). In pyparsing version 3.3.0, usage of those synonyms will start emitting `DeprecationWarnings`. In version 4.0.0 (currently planned not before 2026), the synonyms will be removed, so that usage of the legacy names will begin to raise various Python exceptions.\n\n### Proposed fix\n\nPyparsing 3.2.2 will include a scanner/converter script `pyparsing.tools.cvt_pyparsing_pep8_names` to report needed name changes, and optionally update Python scripts in place (this utility is already [checked in to GitHub](https://github.com/pyparsing/pyparsing/blob/master/pyparsing/tools/cvt_pyparsing_pep8_names.py) if you wish to try it out before that version gets released). The modified scripts should be compatible back to pyparsing 3.0.0, with the exception of those using `delimitedList`, which will require pyparsing 3.1.0. This script can be added to CI automation as a scanner to detect needed changes, and used manually to actually apply the necessary changes.\n\nIn addition, I plan to release at least 1 alpha and 1 beta release of 3.3.0 before a final release, so that the matplotlib team can run it through its paces.\n\nmatplotlib is one of the most significant users of pyparsing, and I would like to be sure that I can maintain compatibility with its uses of this package.","author":{"url":"https://github.com/ptmcg","@type":"Person","name":"ptmcg"},"datePublished":"2025-03-09T20:59:36.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/29722/matplotlib/issues/29722"}