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
We recently ran into an issue with the TOML stub related to the TomlDecodeError. Mypy threw this one at us: "TomlDecodeError" has no attribute "msg". This appears to originate from types-toml, which is maintained from https://github.com/python/typeshed/tree/master/stubs/toml. But it seems that the definition of TomlDecodeError there does not include any of the original class variables, thus generating this error.
Adding this issue for tracking, will possibly update these stubs ourselves in the near future.
The text was updated successfully, but these errors were encountered:
The latest released version of toml doesn't include stubs, so our stubs are still required. But as Akuli mentioned, toml seems to be not longer maintained and I would recommend to switch to tomli. That said, we accept PRs to improve our toml stubs.
We recently ran into an issue with the TOML stub related to the TomlDecodeError. Mypy threw this one at us:
"TomlDecodeError" has no attribute "msg"
. This appears to originate from types-toml, which is maintained from https://github.com/python/typeshed/tree/master/stubs/toml. But it seems that the definition ofTomlDecodeError
there does not include any of the original class variables, thus generating this error.Adding this issue for tracking, will possibly update these stubs ourselves in the near future.
The text was updated successfully, but these errors were encountered: