Replies: 3 comments 1 reply
-
|
This seems to be more of a complaint, than a bug report. If there's a bug or breaking change in v1.10.3, please create an issue to report it, with as much detail as possible. If you just want to complain, please don't use open source, volunteer maintained software. You might also include whether this is fixed in v1.10.4? |
Beta Was this translation helpful? Give feedback.
-
|
It's a request for information (also known as a question), because I don't know that it's pydantic that's broken, or SSLyze doing something wrong. All I know is that if I I can't really give you a detailed bug report, because that's it, and because I don't even know if pydantic is the right place to open a bug report. If you can point me at a way of figuring out where the bug is, I'll do that. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for adding more context. Is this specific to python 3.7? Most likely this was caused by #4880, which in turn was designed to fix other subtle problems with dataclasses. See #4880 added Honestly, I'm not sure where to go from here - dataclass support now has many many subtleties and ever fix we (mostly @PrettyWood 🙏) implements, seems to break some other edge case. dataclass support should be radically simplified in V2, see #4670, but until then I'm not sure what we can really do about this. |
Beta Was this translation helpful? Give feedback.
-
|
Let's continue discussion on #4907, this should have been an issue, not a discussion. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As seen in nabla-c0d3/sslyze#586 SSLyze broke, despite pydantic only doing point releases that should not change its API.
Freezing pydantic at 1.10.2 fixes the issue for now, but I still wanted to ask if this is a bug in pydantic or in SSLyze's usage of pydantic.
Beta Was this translation helpful? Give feedback.
All reactions