11–19 of 19 posts
Unfortunately, people don't know they are made to be stripped in prod with `-OO` so that the perf hit is zero. This means you can never be sure a 3rd party lib you depend on is not using an assert somewhere for a very important check you are going to disable.
https://www.bitecode.dev/p/the-best-python-feature-you-canno...
At this point just use Java instead.
One of the most 'nice' thing about contract systems is automating blame checking in higher-order code. They handle the lambda/method param wrapping and blame direction assignment for you, which is annoying to do via manual assertions. I didn't see a link to DBC, is that in there? Or some other use of contracts that is hard via just asserts, like in test amplification? We are always looking for ways to improve our Pyt…
Python shouldn't need special lib to design by contract, `assert cond, "reason"` and `if __debug__` work very well for that. Unfortunately, people don't know they are made to be stripped in prod with `-OO` so that the perf hit is zero. This means you can never be sure a 3rd party lib you depend on is not using an assert somewhere for a very important check you are going to disable. https://www.bitecode.dev/p/the-best…
This approach ensures only a single point of validation, a lower mental overhead as you are certain it is valid everywhere, and fast failure when it's not - by contract, even.
There are a few places where this concept is discussed, but the most concise phrase is: “Parse, don’t validate.”
Zod (TypeScript) is a good example of a library like this, as it is oriented around types. I’m not sure if Python has something similar.
However, overvalidation can make your code overly verbose, which is something I’ve fallen into before. Use it sparingly.
One of the most 'nice' thing about contract systems is automating blame checking in higher-order code. They handle the lambda/method param wrapping and blame direction assignment for you, which is annoying to do via manual assertions. I didn't see a link to DBC, is that in there? Or some other use of contracts that is hard via just asserts, like in test amplification? We are always looking for ways to improve our Pyt…
It's at the end of the article in one of those "card" links. https://gitlab.com/leogermond/python-dbc
One of the most 'nice' thing about contract systems is automating blame checking in higher-order code. They handle the lambda/method param wrapping and blame direction assignment for you, which is annoying to do via manual assertions. I didn't see a link to DBC, is that in there? Or some other use of contracts that is hard via just asserts, like in test amplification? We are always looking for ways to improve our Pyt…
It's at the end of the article in one of those "card" links. https://gitlab.com/leogermond/python-dbc
I was hoping something like a more modern https://dl.acm.org/doi/10.1145/581478.581484
This isn't meant as a dig, I'm genuinely curious: how is this not simply imposing static typing in python?