This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients barry, maxking, msapiro, p-ganssle, r.david.murray, xtreak
Date 2019-05-17.13:08:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1558098515.11.0.125878006703.issue36564@roundup.psfhosted.org>
In-reply-to
Content
As for the other, I don't see the need for a custom error.  It's a ValueError in my view.  I wouldn't object to it strongly, but note that this error is content dependent.  If there's nothing to encode, you can "get away with" a shorter maxlen.  Though why you would want to is beyond me, and that's another reason I don't think this warrants a custom error class.
History
Date User Action Args
2019-05-17 13:08:35r.david.murraysetrecipients: + r.david.murray, barry, msapiro, maxking, p-ganssle, xtreak
2019-05-17 13:08:35r.david.murraysetmessageid: <1558098515.11.0.125878006703.issue36564@roundup.psfhosted.org>
2019-05-17 13:08:35r.david.murraylinkissue36564 messages
2019-05-17 13:08:34r.david.murraycreate