*** This bug is a duplicate of bug 1247643 ***
https://bugs.launchpad.net/bugs/1247643
** This bug has been marked a duplicate of bug 1247643
Invalid strings in Dateutil 2.2 now cause TypeError instead of ValueError
--
You received this bug notification because you are a member of Ubuntu
** Changed in: python-dateutil (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: hundredpapercuts
Status: Confirmed => Fix Released
** Changed in: dateutil
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Changed in: python-dateutil (Ubuntu)
Importance: Undecided = High
** Changed in: dateutil
Status: New = Confirmed
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New = Confirmed
** Changed in:
This bug was fixed in version 2.3. Current version of dateutil is 2.4.x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438242
Title:
parse() on an invalid time string no longer raises ValueError
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-dateutil (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438242
** Also affects: dateutil
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438242
Title:
parse() on an invalid time string no longer raises ValueError
To