Open rlratzel opened 1 month ago
Yes, it's my fault, I thought parse
is using parse_fp
under the hood, but it's not.
Released a beta version v0.5.2b1
which contains the fix.
Bitten by the same bug, Pls yank version v0.5.0 and v0.5.1.
Appreciated!
I released v0.5.2b2
which also contains a bugfix that some user needs in a hurry. I will release v0.5.2
tomorrow if no one report bug about it. I notified some users to test the v0.5.2b2
.
Yank v0.5.0
and v0.5.1
is not a good choice because I see some user are already using it and pined the version to 0.5.
v0.5.2
just released.
After installing thriftpy2 0.5.1, the following traceback was encountered when calling
parse_fp()
:Perhaps the change to
parse()
done in this PR should also be applied toparse_fp()
?