commit 32e37a12f0255ee5fd5028f5e0a9181f597d35d3 Author: Matt Traudt sirmatt@ksu.edu Date: Mon Jun 25 15:13:35 2018 -0400
Allow datetime objects --- CONTRIBUTING.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index bdbdd99..b72d118 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -40,7 +40,7 @@ commits that show up in ``git blame`` 10 years from now make more sense. Coding Guidelines =================
-**Strongly prefer Unix timestamps** over ``datetime`` structures and always +**Strongly prefer Unix timestamps or datetime objects in UTC** and always work in UTC for as long as possible. When reading/writing/manipulating results from some period of time in the past, always err on the side of caution. For example, open an extra file into the past just in case it happens to include