Mailman 3 October 2015 - NumPy-Discussion

Interesting discussion on copyrighting files.
by Charles R Harris Oct. 17, 2015

Oct. 17, 2015

Worth a read at A&D <http://esr.ibiblio.org/?p=6867#more-6867>. Chuck

3 2

Bug
by josef.pktd＠gmail.com Oct. 16, 2015

Oct. 16, 2015

1 1

how is toolchain selected for compiling (OS X with python.org build)?
by Andrew Jaffe Oct. 15, 2015

Oct. 15, 2015

This isn't, strictly speaking, a numpy question, but I suspect it's something that numpy devs and users have some insight into. I am trying to compile an extension that requires a fairly advanced c++ compiler. Using the built-in apple python, it defaults to the latest clang from apple, and it works just fine. Using the python.org framework build, it still selects clang, which is in principle a new enough compiler, but for some reason it seems to end up pointing to /usr/include/c++/4.2.1/ … [View More]

2 1

A regression in numpy 1.10: VERY slow memory mapped file generation
by Nadav Horesh Oct. 15, 2015

Oct. 15, 2015

I have binary files of size range between few MB to 1GB, which I read process as memory mapped files (via np.memmap). Until numpy 1.9 the creation of recarray on an existing file (without reading its content) was instantaneous, and now it takes ~6 seconds (system: archlinux on sandy bridge). A profiling (using ipython %prun) top of the list is: ncalls tottime percall cumtime percall filename:lineno(function) 21&… [View More]

2 2

Numpy 1.10.1 released.
by Charles R Harris Oct. 14, 2015

Oct. 14, 2015

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 resulted in a failure to parse the version. NumPy 1.10.1 Release Notes ************************** This release deals with a few build problems that showed up in 1.10.0. Most users would not have … [View More]

6 7

Make all comparisons with NaT false?
by Stephan Hoyer Oct. 13, 2015

Oct. 13, 2015

Currently, NaT (not a time) does not have any special treatment when used in comparison with datetime64/timedelta64 objects. This means that it's equal to itself, and treated as the smallest possible value in comparisons, e.g., NaT == NaT and NaT < any_other_time. To me, this seems a little crazy for a value meant to denote a missing/invalid time -- NaT should really have the same comparison behavior as NaN. That is, all comparisons with NaT should be false. The good news is that updating … [View More]

3 2

Deprecating unitless timedelta64 and "safe" casting of integers to timedelta64
by Stephan Hoyer Oct. 13, 2015

Oct. 13, 2015

As part of the datetime64 cleanup I've been working on over the past few days, I noticed that NumPy's casting rules for np.datetime64('NaT') were not working properly: https://github.com/numpy/numpy/pull/6465 This led to my discovery that NumPy currently supports unit-less timedeltas (e.g., "np.timedelta64(5)"), which indicate some sort of generic time difference. The current behavior is to take the time units from the other argument when these are used in a binary operation. Even worse, we … [View More]

3 2

Problem with os.environ.clear in numpy initialization
by Michael Behrisch Oct. 12, 2015

Oct. 12, 2015

-----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 submitted a pull request: https://github.com/behrisch/numpy/pull/1 Although it is mainly a workaround for the bug mentioned, I would be happy if it could get accepted because I have only limited control … [View More]

1 1

1.10 and development version docs
by Ralf Gommers Oct. 11, 2015

Oct. 11, 2015

Hi, I see that there are no docs for 1.10 on docs.scipy.org yet, and the development version docs are from Nov'14. Anyone with permissions want to look at rectifying that situation? Also, building development version docs on TravisCI after each merge would be useful (for Numpy and Scipy). A little more work, but unlike updating the current docs you don't need doc server permissions so can be done by anyone. Here's a more concrete idea of how to achieve this https://github.com/scipy/scipy/… [View More]

2 2

Re: [Numpy-discussion] method to calculate the magnitude squared
by Phillip Feldman Oct. 11, 2015

Oct. 11, 2015

My apologies for the slow response; I was experiencing some technical problems with e-mail. In answer to Antoine's question, my main desire is for a numpy ndarray method, for the convenience, with a secondary goal being improved performance. I have added the function `magsq` to my library, but would like to access it as a method rather than as a function. I understand that I could create a class that inherits from NumPy and add a `magsq` method to that class, but this has a number of disadvantages. Phillip

5 9