Evens Fortuné <evens.fort...@gmail.com> added the comment:

Yes we could say that the documentation can be lacking but that doesn't means 
it's a bug in the code. If you feel that the documentation need to be improved 
then you should submit a patch to the documentation and not how the code should 
be changed. 

If you feel that the error message doesn't give enough information you could 
modify the source code of that module and submit a patch instead of a 
workaround.

But meanwhile I would suggest that your code should check that all the 
information is valid before you submit it to the database. It shouldn't be 
really the responsibility of the database to catch this kind of errors.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue41638>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to