Handle dates before 1900 during indexing (py2 only) #2256
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes indexing with date before 1900. This should not theoretically happen because there is only
created_atandlast_modifiedbut some harvested dataset can have this issue.This is a Python 2 only fix as the "before 1900" limitation has been removed in Python 3 (and so
udata.utils.to_iso*helpers can be safely removed frompy3branches and rely on the builtindatetime.isoformat(timespec='seconds'))(fix datagouv/data.gouv.fr#140 part 2)