Ouranosinc / xscen / 13728641339

90%

push

github

Use date_parser for standardize_periods (#547)

<!-- Please ensure the PR fulfills the following requirements! -->
<!-- If this is your first PR, make sure to add your details to the
AUTHORS.rst! -->
### Pull Request Checklist:
- [x] This PR addresses an already opened issue (for bug fixes /
features)
    - This PR fixes #546 
- [x] (If applicable) Documentation has been added / updated (for bug
fixes / features).
- [x] (If applicable) Tests have been added.
- [ ] This PR does not seem to break the templates.
- [x] CHANGELOG.rst has been updated (with summary of main changes).
- [x] Link to issue (:issue:`number`) and pull request (:pull:`number`)
has been added.

### What kind of change does this PR introduce?
- Adds `period=[pd.Timestamp, pd.Timestamp]` and
`period=["%Y-%m-%dT%H:%M:%S","%Y-%m-%dT%H:%M:%S"]` capability for
dc.search

### Does this PR introduce a breaking change?
- It shouldn't. xs.utils.standardize_periods uses `out_dtype='str'` by
default, which emits only the year. This is equivalent to the old way of
doing things.

### Other information:
- Changes to `xs.utils.standardize_periods`, mostly. Also removes
duplicated calls to standardize_periods in `dc.search` and
`xs.extract.search_data_catalogs`

10 of 10 new or added lines in 3 files covered. (100.0%)

3955 of 4498 relevant lines covered (87.93%)

5.19 hits per line