We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doing so breaks encapsulation and is confusing. Worse, could lead to bugs like this:
try: do some non-encodium thing. except ValidationError: this should only happen when my validation error is raised
and now you might accidentally miss the encodium error (or vice versa)
The text was updated successfully, but these errors were encountered:
Yeah, this was because I had a ValidationError too but used from encodium import *
from encodium import *
Leave this open so we can fix it properly longer term
-----BEGIN EMAIL SIG----- Max Kaye https://xk.io github.com/XertroV -----END EMAIL SIG-----
On Tue, Jul 1, 2014 at 5:38 AM, Kitten Tofu [email protected] wrote:
Doing so breaks encapsulation and is confusing. Worse, could lead to bugs like this: try: do some non-encodium thing.except ValidationError: this should only happen when my validation error is raised and now you might accidentally miss the encodium error (or vice versa) — Reply to this email directly or view it on GitHub #6.
try: do some non-encodium thing.except ValidationError: this should only happen when my validation error is raised
— Reply to this email directly or view it on GitHub #6.
Sorry, something went wrong.
No branches or pull requests
Doing so breaks encapsulation and is confusing. Worse, could lead to bugs like this:
and now you might accidentally miss the encodium error (or vice versa)
The text was updated successfully, but these errors were encountered: