[Numpy-svn] [numpy/numpy] ee6071: BUG: Add a gap in NPY_DATETIMEUNIT enum where 1.6 ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/numpy/numpy
  Commit: ee607114d440023d5c717faecaa1368ea0ffa137
      https://github.com/numpy/numpy/commit/ee607114d440023d5c717faecaa1368ea0ffa137
  Author: Mark Wiebe <mwwiebe at gmail.com>
  Date:   2012-06-05 (Tue, 05 Jun 2012)

  Changed paths:
    M numpy/core/include/numpy/ndarraytypes.h
    M numpy/core/src/multiarray/datetime.c
    M numpy/core/src/multiarray/scalartypes.c.src

  Log Message:
  -----------
  BUG: Add a gap in NPY_DATETIMEUNIT enum where 1.6 had the busday unit

1.7 doesn't have the business day unit, but instead provides
a separate business day API. For binary compatibility, as
experienced in Pandas use of datetime64, it's a good idea for
the numbers to stay the same.


  Commit: f2a7464e3b879f2d43709da5f2e456285d107f30
      https://github.com/numpy/numpy/commit/f2a7464e3b879f2d43709da5f2e456285d107f30
  Author: Travis E. Oliphant <teoliphant at gmail.com>
  Date:   2012-06-12 (Tue, 12 Jun 2012)

  Changed paths:
    M numpy/core/include/numpy/ndarraytypes.h
    M numpy/core/src/multiarray/datetime.c
    M numpy/core/src/multiarray/scalartypes.c.src

  Log Message:
  -----------
  Merge pull request #295 from mwiebe/datetime_unit_16compat

BUG: Add a gap in NPY_DATETIMEUNIT enum where 1.6 had the busday unit


Compare: https://github.com/numpy/numpy/compare/db5168b15744...f2a7464e3b87