parse() on an invalid time string no longer raises ValueError
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Fix Released
|
High
|
Unassigned | ||
dateutil |
Fix Released
|
Undecided
|
Unassigned | ||
python-dateutil (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
utopic:
⟫ python -c "from dateutil.parser import parse; parse('X')"
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/
return DEFAULTPARSER.
File "/usr/lib/
raise ValueError, "unknown string format"
ValueError: unknown string format
vivid:
$ python -c "from dateutil.parser import parse; parse('X')"
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/
return DEFAULTPARSER.
File "/usr/lib/
res, skipped_tokens = self._parse(
TypeError: 'NoneType' object is not iterable
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: python-dateutil 2.2-2
ProcVersionSign
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
Date: Mon Mar 30 14:41:44 2015
PackageArchitec
SourcePackage: python-dateutil
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in python-dateutil (Ubuntu): | |
importance: | Undecided → High |
Changed in dateutil: | |
status: | New → Confirmed |
Changed in hundredpapercuts: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in python-dateutil (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in hundredpapercuts: | |
status: | Confirmed → Fix Released |
Changed in dateutil: | |
status: | Confirmed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.