You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
As of v3.3.0 (Dec 2025), the pyparsing library has begun emitting DeprecationWarnings for use of non-PEP8-compliant method aliases. These are triggered by bibtexparser.
Question for the pr: is nudging the pyparsing dependency up to 3.0 from its current 2.0 (or so) acceptable, or is it necessary to maintain support for the older library? The now-deprecated aliases were added in 3.0, so it'll be a more complex patch to support both.
Yep, I don't see any problem there. Current constaint sais 'pyparsing>=2.0.3', so most users will be on 3.x anyways, and compatibility should also be given.
Activity
MiWeiss commentedon Jan 14, 2026
Hi @jennifer-richards .
Thanks for offering to contribute a PR. I am looking forward to reviewing it.
Attention: This issue refers to
bibtexparser v1(which lives on a separate branch, not the main branch - check the README)jennifer-richards commentedon Jan 15, 2026
Question for the pr: is nudging the pyparsing dependency up to 3.0 from its current 2.0 (or so) acceptable, or is it necessary to maintain support for the older library? The now-deprecated aliases were added in 3.0, so it'll be a more complex patch to support both.
[-]Deprecation warnings from pyparser library[/-][+]Deprecation warnings from pyparsing library[/+]MiWeiss commentedon Jan 15, 2026
Yep, I don't see any problem there. Current constaint sais 'pyparsing>=2.0.3', so most users will be on 3.x anyways, and compatibility should also be given.
MiWeiss commentedon Jan 29, 2026
Clodes in #512, and released in 1.4.4. Thanks @jennifer-richards