| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | fix class reference for iso8601.Utc in module docstringfix-module-docstring | Felix Schwarz | 2016-02-12 | 1 | -1/+1 |
| | | | | | | | | | | The reference to "iso8601.iso8601.Utc" is not wrong but not what Utc.__repr__() actually returns (since 29752e308996). In Python 3.2+ we use Python's UTC implementation (so we get a different __repr__() output) but I guess that won't confuse users too much. | ||||
| * | Export FixedOffset in __all__ | Julien Danjou | 2016-01-26 | 1 | -1/+2 |
| | | | | | Fixes #20 | ||||
| * | Fix FixedOffset comparison | Julien Danjou | 2015-11-18 | 1 | -3/+1 |
| | | | | | Fixes #19 | ||||
| * | Do not use custom timezone implementation on Python ? 3.2 | Julien Danjou | 2015-11-08 | 1 | -49/+55 |
| | | | | | | | | Python ? 3.2 has a timezone class that we can use directly for FixedOffset and UTC. Fixes #17 | ||||
| * | Remove debug logging | Quentin Pradet | 2015-10-30 | 1 | -5/+0 |
| | | |||||
| * | Add support for , as separator for fractional part | Linus Wallgren | 2015-07-01 | 1 | -1/+1 |
| | | |||||
| * | Adding API reference to docs | Michael Twomey | 2014-02-27 | 1 | -2/+14 |
| | | |||||
| * | Fix parsing of YYYY-MM and add YYYY | Michael Twomey | 2014-02-27 | 1 | -20/+33 |
| | | | | | | | Fixes #14 (https://bitbucket.org/micktwomey/pyiso8601/issue/14/regression-yyyy-mm-no-longer-parses) Bump version to 1.10 | ||||
| * | tests: fix remaining tests | Julien Danjou | 2014-02-18 | 1 | -3/+2 |
| | | |||||
| * | Raise error on YYYYMM or YYMMDD | Julien Danjou | 2014-02-18 | 1 | -8/+10 |
| | | |||||
| * | Raise error when parsing year with wrong number for years | julien | 2014-02-18 | 1 | -16/+20 |
| | | | | | Closes #12 | ||||
| * | Fix for regression when parsing microseconds | Davanum Srinivas | 2013-10-18 | 1 | -1/+1 |
| | | |||||
| * | Handle negative timezone offsets correctly0.1.6 | Michael Twomey | 2013-10-18 | 1 | -0/+1 |
| | | | | | | | | | | | I had dropped the negative minutes in a braino and had incorrectly updated tests to match. I've added a isoformat field to the tests, so I can correctly assert they formatted date looks right. Thanks to Jonathan Lange for reporting this and a patch. Fixes #8 | ||||
| * | Handle compact date format | Michael Twomey | 2013-10-17 | 1 | -1/+1 |
| | | | | | | | Thanks to rvandolson@esri.com Fixes #6 | ||||
| * | Z always specifies UTC now | Michael Twomey | 2013-10-17 | 1 | -1/+1 |
| | | | | | | | Thanks to vfaronov Fixes #5 | ||||
| * | Fix pickling / deepcopy of returned datetime objects | Michael Twomey | 2013-10-17 | 1 | -0/+5 |
| | | | | | | | Thanks to fogathmann and john@openlearning.com Fixes #3 | ||||
| * | Fix microsecond rounding issues | Michael Twomey | 2013-10-17 | 1 | -2/+4 |
| | | | | | | | Thanks to nielsenb@jetfuse.net Fixes #2 | ||||
| * | Rewrote the regex, large parts of the code and tests | Michael Twomey | 2013-10-16 | 1 | -25/+87 |
| | | | | | Added more tests to cover more of the spec and fixed many edge cases. | ||||
| * | Correctly raise ParseError for more invalid inputs | Michael Twomey | 2013-10-15 | 1 | -3/+6 |
| | | | | | | | Fixes #1 Thanks to manish.tomar | ||||
| * | Make the inclusion of seconds optional in the date format. | Chris Down | 2013-09-08 | 1 | -5/+7 |
| | | | | | | | ISO 8601 specifies that the inclusion of seconds in the date format is optional. To accommodate this, if the seconds are not included, it is considered to be 0. | ||||
| * | Applied python 3 support patch from ↵ | Michael Twomey | 2013-08-29 | 1 | -1/+8 |
| | | | | | | | https://code.google.com/p/pyiso8601/issues/detail?id=23 Also updated to use tox and py.test | ||||
| * | Importing r23 / 0.1.4 from https://code.google.com/p/pyiso8601/ | Michael Twomey | 2013-08-29 | 1 | -0/+102 |
 |
index : delta/pyiso8601.git | |
| bitbucket.org: micktwomey/pyiso8601 |
| summaryrefslogtreecommitdiff |