Skip to content

Releases: geospace-code/sciencedates

Python >= 3.7, update type anno

29 Dec 04:56
8cfe354
Compare
Choose a tag to compare
v1.5.1

Python >= 3.7 anno, src layout

refactor

20 May 03:53
Compare
Choose a tag to compare
  • black code style
  • put functions into multiple files for easier management (all one import still)

CI template Github Action

11 Nov 22:28
3176507
Compare
Choose a tag to compare
  • apply best practices for python projects
  • move CI to github actions

Py35 compatible, modularize

09 Sep 12:44
17b9d18
Compare
Choose a tag to compare
  • Add PyPy3 and Python 3.5 compatibility
  • modularize
  • remove mandatory timezone components

Robustness

20 Jul 16:15
a9dad9c
Compare
Choose a tag to compare
  • improve test coverage and types tested

modernize

10 Jul 21:58
Compare
Choose a tag to compare
  • functionalize tests
  • improve test coverage
  • setup.cfg <= setup.py
  • RST=>md

Enable arrays

03 Jun 21:03
Compare
Choose a tag to compare

Enable np.ndarray in/out for most functions.

Timezone naive expected

03 Jun 20:15
Compare
Choose a tag to compare

Due to upcoming changes in Numpy deprecating timezone-aware handling by numpy.datetime64, and the numerous essential libraries which depend on Numpy,
we have defaulted to timezone-naive.

The .forceutc() function still allows coercing to UTC if desired, but this is no longer used internally as it used to be.

Also CI now uses flake8 and mypy type checking. As usual, type checking helped uncover some corner cases.

handle datetime.date correctly too

27 Feb 07:11
Compare
Choose a tag to compare
v1.3.2

handle datetime.datetime vs datetime.date correctly

forceutc returns datetime.time unchanges

27 Feb 06:52
Compare
Choose a tag to compare

allow datetime.date that comes into forceutc() to return unchanged.