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
Since the v0.2.5 release, I have noticed a problem with the fallback encoder in the escape_item() function of the library. Previously, if I provided a value that was not directly listed in the encoder list, escape_item() would fall back to the default encoder, encode_str(), and it worked correctly. However, after the commit referenced here, a type declaration was added for encode_str(), which caused it to fail during type checks and can no longer be used as a default encoder.
I encountered this issue when using the FakeDate class from the freezegun library. FakeDate wraps datetime.date objects and relies on the default encoder.
To help address this issue, I plan to create a pull request that includes a reproduction of the problem.
The text was updated successfully, but these errors were encountered:
Since the v0.2.5 release, I have noticed a problem with the fallback encoder in the escape_item() function of the library. Previously, if I provided a value that was not directly listed in the encoder list, escape_item() would fall back to the default encoder, encode_str(), and it worked correctly. However, after the commit referenced here, a type declaration was added for encode_str(), which caused it to fail during type checks and can no longer be used as a default encoder.
I encountered this issue when using the FakeDate class from the freezegun library. FakeDate wraps datetime.date objects and relies on the default encoder.
To help address this issue, I plan to create a pull request that includes a reproduction of the problem.
The text was updated successfully, but these errors were encountered: