[Numpy-discussion] Numpy 1.10.0 release

Hi All, It is my pleasure to release NumPy 1.10.0. Files may be found at Sourceforge and pypi . This release is the result of 789 non-merge commits made by 160 developers over a

Re: [Numpy-discussion] Let's move forward with the current governance document.

On Mon, Oct 5, 2015 at 1:50 PM, Sturla Molden wrote: > > Nathaniel Smith wrote: > > > Thanks Chuck! It looks like it's just wording tweaks / clarifications > > at this point, so nothing we need to discuss in detail on the list. If > > anyone wants to

[Numpy-discussion] ANN: bcolz 0.11.3 released!

=== Announcing bcolz 0.11.3 === What's new == Implemented new feature (#255): bcolz.zeros() can create new ctables too, either empty or filled with zeros. (#256 @FrancescElies @FrancescAlted). Also, in previous, non announced versions (0.11.1 and

Re: [Numpy-discussion] Let's move forward with the current governance document.

Nathaniel Smith wrote: > Are you planning to go around vetoing things I don't consider myself qualified. > for ridiculous reasons and causing havoc? That would be unpolite. > And if not, then who is it that you're worried about? I am not sure :) I just envisioned a Roman

Re: [Numpy-discussion] Let's move forward with the current governance document.

There is the concept of consensus-driven development, which centers on veto rights. It does assume that all actors are driven by a common goal to improve the project. For example, the fact that we didn't have consensus back during the whole NA brouhaha was actually a good thing because IMHO

Re: [Numpy-discussion] Cython-based OpenMP-accelerated quartic polynomial solver

On 02/10/15 13:05, Daπid wrote: Have you tried asking Python-dev for help with this? Hopefully they would have some weight there. It seems both GCC dev and Apple (for GCD and Accelerate) has taken a similar stance on this. There is tiny set of functions the POSIX standard demands should

Re: [Numpy-discussion] Cython-based OpenMP-accelerated quartic polynomial solver

On Mon, Oct 5, 2015 at 2:52 PM, Sturla Molden wrote: > On 02/10/15 13:05, Daπid wrote: > >> Have you tried asking Python-dev for help with this? Hopefully they >> would have some weight there. > > It seems both GCC dev and Apple (for GCD and Accelerate) has taken a

Re: [Numpy-discussion] Cython-based OpenMP-accelerated quartic polynomial solver

On Mon, Oct 5, 2015 at 3:05 PM, Nathaniel Smith wrote: > On Mon, Oct 5, 2015 at 2:52 PM, Sturla Molden wrote: >> On 02/10/15 13:05, Daπid wrote: >> >>> Have you tried asking Python-dev for help with this? Hopefully they >>> would have some weight there.

Re: [Numpy-discussion] [pydata] ANN: pandas v0.17.0rc2 - RELEASE CANDIDATE 2

it should be exactly the same (they are going to release soon as well I think) - with an updated version > On Oct 5, 2015, at 2:25 PM, Big Stone wrote: > > hi, > > on pypi, pandas_datareader (0.1.1) is dated from April 10th. > > Is it up-to-date with pandas 0.17rc2 ? >

Re: [Numpy-discussion] Let's move forward with the current governance document.

On Mon, Oct 5, 2015 at 2:11 PM, Sturla Molden wrote: > I just envisioned a Roman patron shouting veto or a US senator > filibustering. Expulsion would be the appropriate recation, yes :-) Oh if only the US Senate could expulse people! -sigh -- Christopher Barker,

Re: [Numpy-discussion] Let's move forward with the current governance document.

Nathaniel Smith wrote: > Thanks Chuck! It looks like it's just wording tweaks / clarifications > at this point, so nothing we need to discuss in detail on the list. If > anyone wants to watch the sausage being made, then the link is above > :-), and we'll continue the discussion

[Numpy-discussion] Should we drop support for "one file" compilation mode?

Hi all, For a long time, NumPy has supported two different ways of being compiled: "Separate compilation" mode: like most C projects, each .c file gets compiled to a .o file, and then the .o files get linked together to make a shared library. (This has been the default since 1.8.0.) "One file"

Re: [Numpy-discussion] Should we drop support for "one file" compilation mode?

On Mon, 5 Oct 2015 15:26:17 -0700 Nathaniel Smith wrote: > Hi all, > > For a long time, NumPy has supported two different ways of being compiled: > > "Separate compilation" mode: like most C projects, each .c file gets > compiled to a .o file, and then the .o files get linked

[Numpy-discussion] NumPy Governance Document.

Hi All The NumPy Governance Document has been merged and is now in effect. Thanks to all who contributed to the discussion. And a special thanks to Nathaniel, who wrote the draft and kept it up to date as the discussion progressed. Chuck

Re: [Numpy-discussion] NumPy Governance Document.

> > > The NumPy Governance Document > has been merged and is now in effect. > whoo hoo! And a special thanks to Nathaniel, > Indeed -- and everyone else that put a lot of their time into the discussion. Looking forward to discussing technical issues

Re: [Numpy-discussion] method to calculate the magnitude squared

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