I thought I'd add a little more specifically about the kind of
graphics/point cloud work I'm doing right now at Thinkbox, and how it
relates. To echo Francesc's point about NumPy already being an industry
standard, within the VFX/graphics industry there is a reference platform
definition on Linux,
On Tue, Aug 25, 2015 at 12:21 PM, Antoine Pitrou solip...@pitrou.net wrote:
On Tue, 25 Aug 2015 03:03:41 -0700
Nathaniel Smith n...@pobox.com wrote:
Supporting third-party dtypes
~
[...]
Some features that would become straightforward to implement
(e.g.
Hi Travis,
Thanks for taking the time to write up your thoughts!
I have many thoughts in return, but I will try to restrict myself to two
main ones :-).
1) On the question of whether work should be directed towards improving
NumPy-as-it-is or instead towards a compatibility-breaking
[Popping this off to its own thread to try and keep things easier to follow]
On Tue, Aug 25, 2015 at 9:52 AM, Nathan Goldbaum nathan12...@gmail.com wrote:
- Lament: it would be really nice if we could get more people to
test our beta releases, because in practice right now 1.x.0 ends
On Tue, Aug 25, 2015 at 5:53 PM, David Cournapeau courn...@gmail.com wrote:
Thanks for the good summary Nathaniel.
Regarding dtype machinery, I agree casting is the hardest part. Unless the
code has changed dramatically, this was the main reason why you could not
make most of the dtypes
On Wed, Aug 26, 2015 at 10:11 AM, Antoine Pitrou solip...@pitrou.net
wrote:
On Wed, 26 Aug 2015 16:45:51 + (UTC)
Irwin Zaid iz...@continuum.io wrote:
So, we see DyND is having a twofold purpose. The first is to expand upon
the
kinds of data that NumPy can represent and do
Indeed, the helper function I wrote for xray was not designed to handle
None/np.newaxis or non-1d Boolean indexers, because those are not valid
indexers for xray objects. I think it could be straightforwardly extended
to handle None simply by not counting them towards the total number of
On Wed, 26 Aug 2015 16:45:51 + (UTC)
Irwin Zaid iz...@continuum.io wrote:
So, we see DyND is having a twofold purpose. The first is to expand upon the
kinds of data that NumPy can represent and do computations upon. The second
is to provide a standard array package that can cross the
26.08.2015, 14:14, Francesc Alted kirjoitti:
[clip]
2015-08-25 12:03 GMT+02:00 Nathaniel Smith n...@pobox.com:
Let's focus on evolving numpy as far as we can without major
break-the-world changes (no numpy 2.0, at least in the foreseeable
future).
And, as a target for that evolution,
On Wed, Aug 26, 2015 at 6:11 PM, Antoine Pitrou solip...@pitrou.net wrote:
One possible limitation is that the lingua franca for language
interoperability is C, not C++. DyND doesn't have to be written in C,
but exposing a nice C API may help make it attractive to the various
language
Hi,
Splitting this one off too because it's a rather different discussion,
although related.
On Tue, Aug 25, 2015 at 11:03 AM, Nathaniel Smith n...@pobox.com wrote:
[snip]
Formalizing our governance/decision making
==
This was a major focus of
Hello everyone,
Mark and I thought it would be good to weigh in here and also be explicitly
around to discuss DyND. To be clear, neither of us has strong feelings on
what NumPy *should* do -- we are both long-time NumPy users and we both see
NumPy being around for a while. But, as Francesc
Hi Matthew
On 2015-08-26 10:50:47, Matthew Brett matthew.br...@gmail.com
wrote:
In short, the core structure seems to be characteristically
associated with a conservatism and lack of vision that causes
the project to stagnate.
Can you describe how a democratic governance structure would
Hi all,
Can anyone give me some advice for translating this equation into code
using numpy?
eta(t) = lim(dt - 0) N(0, 1/sqrt(dt)),
where N(a, b) is a Gaussian random variable of mean a and variance b**2.
This is a heuristic definition of a white noise process.
Thanks,
Dan
As a Matplotlib developer I try to test our code manually with all betas
and rc of new numpy versions.
(And already pushed fixed a few new deprecation warnings with 1.10beta1
which otherwise passes our test suite.
I forgot to report this back since there were no issues to report )
However, we
On Mi, 2015-08-26 at 00:05 -0700, Nathaniel Smith wrote:
On Tue, Aug 25, 2015 at 5:53 PM, David Cournapeau courn...@gmail.com wrote:
Thanks for the good summary Nathaniel.
Regarding dtype machinery, I agree casting is the hardest part. Unless the
code has changed dramatically, this was
Hello,
The SourceForge download page for 1.10.0b1 mentions:
89e467cec774527dd254c1e039801726db1367433053801f0d8bc68deac74009
numpy-1.10.0b1.tar.gz
But after downloading the file I get:
$ sha256sum numpy-1.10.0b1.tar.gz
855695405092686264dc8ce7b3f5c939a6cf1a5639833e841a5bb6fb799cd6a8
The file is also not signed so the checksums are not trustworthy anyway.
Please sign the releases as we did in the past.
On 08/26/2015 10:28 AM, Antoine Pitrou wrote:
Hello,
The SourceForge download page for 1.10.0b1 mentions:
On Wed, Aug 26, 2015 at 2:28 AM, Antoine Pitrou solip...@pitrou.net wrote:
Hello,
The SourceForge download page for 1.10.0b1 mentions:
89e467cec774527dd254c1e039801726db1367433053801f0d8bc68deac74009
numpy-1.10.0b1.tar.gz
But after downloading the file I get:
$ sha256sum
Hi,
Thanks Nathaniel and others for sparking this discussion as I think it is
very timely.
2015-08-25 12:03 GMT+02:00 Nathaniel Smith n...@pobox.com:
Let's focus on evolving numpy as far as we can without major
break-the-world changes (no numpy 2.0, at least in the foreseeable
future).
Hi,
On Wed, Aug 26, 2015 at 7:59 AM, Nathaniel Smith n...@pobox.com wrote:
[Popping this off to its own thread to try and keep things easier to follow]
On Tue, Aug 25, 2015 at 9:52 AM, Nathan Goldbaum nathan12...@gmail.com
wrote:
- Lament: it would be really nice if we could get more
On Wed, Aug 26, 2015 at 7:32 AM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Wed, Aug 26, 2015 at 7:31 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Wed, Aug 26, 2015 at 7:11 AM, Antoine Pitrou solip...@pitrou.net
wrote:
On Tue, 25 Aug 2015 10:26:02 -0600
Charles
On Wed, Aug 26, 2015 at 1:41 AM, Nathaniel Smith n...@pobox.com wrote:
Hi Travis,
Thanks for taking the time to write up your thoughts!
I have many thoughts in return, but I will try to restrict myself to two
main ones :-).
1) On the question of whether work should be directed towards
On Tue, 25 Aug 2015 10:26:02 -0600
Charles R Harris charlesr.har...@gmail.com wrote:
Hi All,
The silence after the 1.10 beta has been eerie. Consequently, I'm thinking
of making a first release candidate this weekend. If you haven't yet tested
the beta, please do so. It would be good to
Pandas has for quite a while has a travis build where we install numpy
master and then run our test suite.
e.g. here: https://travis-ci.org/pydata/pandas/jobs/77256007
Over the last year this has uncovered a couple of changes which affected
pandas (mainly using something deprecated which was
On Wed, Aug 26, 2015 at 7:31 AM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Wed, Aug 26, 2015 at 7:11 AM, Antoine Pitrou solip...@pitrou.net
wrote:
On Tue, 25 Aug 2015 10:26:02 -0600
Charles R Harris charlesr.har...@gmail.com wrote:
Hi All,
The silence after the 1.10 beta
On Wed, Aug 26, 2015 at 7:11 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Tue, 25 Aug 2015 10:26:02 -0600
Charles R Harris charlesr.har...@gmail.com wrote:
Hi All,
The silence after the 1.10 beta has been eerie. Consequently, I'm
thinking
of making a first release candidate this
Hi,
We've found that NumPy uses the local TZ for printing datetime64 timestamps:
In [22]: t = datetime.utcnow()
In [23]: print t
2015-08-26 11:52:10.662745
In [24]: np.array([t], dtype=datetime64[s])
Out[24]: array(['2015-08-26T13:52:10+0200'], dtype='datetime64[s]')
Googling for a way to
Just a data point, I just tested 1.9.0rc1 (built from source) with
matplotlib master, and things appear to be fine there. In fact, matplotlib
was built against 1.7.x (I was hunting down a regression), and worked
against the 1.9.0 install, so the ABI appears intact.
Cheers!
Ben Root
On Wed, Aug
On Aug 26, 2015 7:03 PM, Benjamin Root ben.v.r...@gmail.com wrote:
Just a data point, I just tested 1.9.0rc1 (built from source) with
matplotlib master, and things appear to be fine there. In fact, matplotlib
was built against 1.7.x (I was hunting down a regression), and worked
against the 1.9.0
Aw, crap... I looked at the list of tags and saw the rc1... I'll test again
in the morning Grumble, grumble...
On Aug 26, 2015 10:53 PM, Nathaniel Smith n...@pobox.com wrote:
On Aug 26, 2015 7:03 PM, Benjamin Root ben.v.r...@gmail.com wrote:
Just a data point, I just tested 1.9.0rc1
31 matches
Mail list logo
