25.08.2015, 01:15, Chris Laumann kirjoitti:
Would it be possible then (in relatively short order) to create
a py2 - py3 numpy pickle converter?
You probably need to modify the pickle stream directly, replacing
*STRING opcodes with *BYTES opcodes when it comes to objects that are
needed for
On 08/24/2015 10:23 AM, Sebastian Berg wrote:
Fabien, just to make sure you are aware. If you are overriding
`__getitem__`, you should also implement `__setitem__`. NumPy does some
magic if you do not. That will seem to make `__setitem__` work fine, but
breaks down if you have advanced
On Tue, 25 Aug 2015 19:12:30 +0300
Pauli Virtanen p...@iki.fi wrote:
25.08.2015, 01:15, Chris Laumann kirjoitti:
Would it be possible then (in relatively short order) to create
a py2 - py3 numpy pickle converter?
You probably need to modify the pickle stream directly, replacing
*STRING
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 discover as many problems as we
can before the first release.
Chuck
On Tue, Aug 25, 2015 at 5:03 AM, Nathaniel Smith n...@pobox.com wrote:
Hi all,
These are the notes from the NumPy dev meeting held July 7, 2015, at
the SciPy conference in Austin, presented here so the list can keep up
with what happens, and so you can give feedback. Please do give
On Tue, Aug 25, 2015 at 4:03 AM, Nathaniel Smith n...@pobox.com wrote:
Hi all,
These are the notes from the NumPy dev meeting held July 7, 2015, at
the SciPy conference in Austin, presented here so the list can keep up
with what happens, and so you can give feedback. Please do give
On Tue, Aug 25, 2015 at 3:58 PM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Tue, Aug 25, 2015 at 1:00 PM, Travis Oliphant tra...@continuum.io
wrote:
Thanks for the write-up Nathaniel. There is a lot of great detail and
interesting ideas here.
snip
I think that summarizes
On Tue, Aug 25, 2015 at 3:58 PM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Tue, Aug 25, 2015 at 1:00 PM, Travis Oliphant tra...@continuum.io
wrote:
Thanks for the write-up Nathaniel. There is a lot of great detail and
interesting ideas here.
snip
There are at least 3
Just an FYI for the upcoming Python release, a very detailed post from
Steve Dower, the Microsoft developer who is now in charge of the Windows
releases for Python, on how the build process will change in 3.5 regarding
extensions:
http://stevedower.id.au/blog/building-for-python-3-5/
Cheers,
f
Thanks for the write-up Nathaniel. There is a lot of great detail and
interesting ideas here.
I've am very eager to understand how to help NumPy and the wider community
move forward however I can (my passions on this have not changed since
1999, though what I myself spend time on has changed).
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. even in third-party libraries) if this were fixed:
- missing value support
Hi all,
These are the notes from the NumPy dev meeting held July 7, 2015, at
the SciPy conference in Austin, presented here so the list can keep up
with what happens, and so you can give feedback. Please do give
feedback, none of this is final!
(Also, if anyone who was there notices anything I
On Tue, Aug 25, 2015 at 1:00 PM, Travis Oliphant tra...@continuum.io
wrote:
Thanks for the write-up Nathaniel. There is a lot of great detail and
interesting ideas here.
I've am very eager to understand how to help NumPy and the wider community
move forward however I can (my passions on
Hi Nathaniel,
Thanks for the notes.
In some sense, the new dtype class(es) will provided a way of
formalizing these `weird` metadata, and probably exposing them to
Python.
May I add that please consider adding a way to declare the sorting
order (priority and direction) of fields in a structured
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 separate from numpy codebase (I tried to move the
datetime dtype out of multiarray
15 matches
Mail list logo
