You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee=Noneclosed_at=<Date2018-05-14.22:22:48.621>created_at=<Date2018-05-14.14:30:10.229>labels= ['3.8', 'type-bug', '3.7']
title='cgi.parse_multipart does not have an associated "errors" parameter with its "encoding" parameter'updated_at=<Date2018-05-15.11:45:32.537>user='https://github.com/hawkowl'
New changeset e8f968d by Ned Deily (Miss Islington (bot)) in branch '3.7': bpo-33497: Add errors param to cgi.parse_multipart and make an encoding in FieldStorage use the given errors (GH-6804) (GH-6837) e8f968d
Is 'replace' the good default value? 'strict' is the default value for most encoding/decoding operations. 'surrogateescape' is used if the failure and the loss of information are not desirable (like in filenames decoding). 'backslashreplace' is good if we want to avoid a failure, but want to expose undecodable bytes in human-readable form.