As has come up repeatedly over the past few years, nobody seems to be very
happy with the way that NumPy's datetime64 type parses and prints datetimes
in local timezones.
The tentative consensus from last year's discussion was that we should make
datetime64 timezone naive, like the standard
On Mon, Oct 12, 2015 at 12:10 AM, Stephan Hoyer wrote:
> As has come up repeatedly over the past few years, nobody seems to be very
> happy with the way that NumPy's datetime64 type parses and prints datetimes
> in local timezones.
>
> The tentative consensus from last year's
Hi All,
I'm pleased to announce the release of Numpy 1.10.1. This release fixes
some build problems and serves to reset the release number on pipy to
something usable. As a note for future release managers, I had to upload
these files from the command line, as using the file upload option at pipy
Hi,
On Mon, Oct 12, 2015 at 9:27 AM, Charles R Harris
wrote:
> Hi All,
>
> I'm pleased to announce the release of Numpy 1.10.1. This release fixes some
> build problems and serves to reset the release number on pipy to something
> usable. As a note for future release
On Mon, Oct 12, 2015 at 3:10 AM, Stephan Hoyer wrote:
> The tentative consensus from last year's discussion was that we should
> make datetime64 timezone naive, like the standard library's
> datetime.datetime
If you are going to make datetime64 more like datetime.datetime,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I am sorry I sent the wrong pull request. Here is the correct one:
https://github.com/numpy/numpy/pull/6460
Best regards,
Michael
Am 12.10.2015 um 20:19 schrieb Michael Behrisch:
> Hi list, I encountered a problem in my code which depends on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi list,
I encountered a problem in my code which depends on numpy. Due to an
unusual variable in my environment and this python bug
https://bugs.python.org/issue20658 the os.environ.clear call in
numpy/core/__init__.py fails. I wrote a patch and
Hi,
Thanks Nathaniel and everyone else who contributed for pushing forward with
formalizing Numpy governance and with this FSA. I'm quite excited about
both!
Before I start commenting on the FSA, I'd like to point out that I'm both
on the numpy steering committee and the NumFOCUS board. I don't