Comment 2 for bug 1247643

Recently ran into this issue. The end result is I can't reliably pass user data to dateutil.parser.parse(), as it may contain an invalid string, but I can't catch the correct exception to handle it.

Any chance of the fix being accepted and rolled into a new version?