-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert ParsingError
to dataclass(frozen=False)
#12
Comments
I just merge a PR to make exceptions non dataclasses. If there are no showstoppers, tomorrow I will try to use it in Pint. |
The release of 0.4 seems to be broken with Pint (currently only 0.24.3). Downgrading flexparser to 0.3.1 does not have this issue. Running Python 3.12.7.
|
This is expected, see the whole discussion thread in hgrecco/pint#2037. It is inevitable to break these two. Hopefully the pint update will come soon to unbreak things. |
Thanks - as a friendly suggestion to the maintainers of Pint and flexparser... I would recommend not doing a breaking release of flexparser whilst knowing that the latest released of Pint only specifies a lower bound dependency on flexparser. |
Unfortunately the opposite (always higher-bounding dependencies) is also a maintenance burden often with no benefits. It's a balancing game and inevitably at any time one party will be affected either by python version incompatibility, dependency breakage, unblocking of higher bound (particularly when it's part of a long chain). My thought is to just hope for timely responses and help with the debugging. |
I am closing this issue as is fixed in Python 0.24.4 Please let me know if you encounter any problem. |
This is a circular issue in combination with hgrecco/pint#2037
Either all of these exceptions are made frozen or unfrozen, we cannot mix each other. On
pint
side the issue is with dual inheritance withAttributeError
which interferes. One option is to relax the frozenness on all pint errors, which includes flexparser as well, or we removeAttributeError
inheritance. @hgrecco thoughts on which one would be preferred, neither of them is ideal unfortunatelyThe text was updated successfully, but these errors were encountered: