On 13 Apr 2016 21:48, "Matthew Brett" <matthew.br...@gmail.com> wrote:
>
> On Wed, Apr 13, 2016 at 1:29 PM, Oscar Benjamin
> <oscar.j.benja...@gmail.com> wrote:
> > On 13 April 2016 at 20:15, Matthew Brett <matthew.br...@gmail.com>
wrote:
> >> Do
On 13 April 2016 at 20:15, Matthew Brett wrote:
> Done. If y'all are on linux, and you have pip >= 8.11, you should
> now see this kind of thing:
That's fantastic. Thanks Matt!
I just test installed this and ran numpy.test(). All tests passed but
then I got a segfault
On 13 January 2016 at 22:23, Chris Barker wrote:
> On Mon, Jan 11, 2016 at 5:29 PM, Nathaniel Smith wrote:
>>
>> I agree that talking about such things on distutils-sig tends to elicit a
>> certain amount of puzzled incomprehension, but I don't think it
On 8 January 2016 at 23:27, Chris Barker wrote:
> On Fri, Jan 8, 2016 at 1:58 PM, Robert McGibbon wrote:
>>
>> I'm not sure if this is the right path for numpy or not,
>
>
> probably not -- AFAICT, the PyPa folks aren't interested in solving teh
>
On 8 Jan 2016 19:07, "Robert McGibbon" wrote:
>
> Does anyone know if there's been any movements with the PyPI folks on
allowing linux wheels to be uploaded?
>
> I know you can never be certain what's provided by the distro, but it
seems like if Anaconda can solve the
On 8 Jan 2016 19:07, "Robert McGibbon" wrote:
>
> Does anyone know if there's been any movements with the PyPI folks on
allowing linux wheels to be uploaded?
>
> I know you can never be certain what's provided by the distro, but it
seems like if Anaconda can solve the
On 3 December 2015 at 08:45, Manolo Martínez wrote:
>> > >> Is there any way to check for cycles in this situation?
>> >
>> > > Fast fourier transform (fft)?
>> >
>> > +1 For using a discrete Fourier transform, as implemented by numpy.fft.fft.
>> > You mentioned that you
On 3 December 2015 at 11:58, Manolo Martínez wrote:
>> > This is doing the job for me at the moment, but there are, that I can
>> > see, a couple of things that could be improved (and surely more that I
>> > cannot see):
>
>> If what you have works out fine for you then
On Tue, 1 Sep 2015 18:43 Phil Hodge <ho...@stsci.edu> wrote:
On 09/01/2015 11:14 AM, Oscar Benjamin wrote:
> Just use the next power of 2. Pure powers of 2 are the most efficient
> for FFT algorithms so it potentially works out better than finding a
> smaller but similarly compos
On 1 September 2015 at 11:38, Joseph Codadeen wrote:
>
>> And while you zero-pad, you can zero-pad to a sequence that is a power of
>> two, thus preventing awkward factorizations.
>
> Does numpy have an easy way to do this, i.e. for a given number, find the
> next highest
On 16 March 2015 at 15:53, Dave Hirschfeld dave.hirschf...@gmail.com wrote:
I have a number of large arrays for which I want to compute the mean and
standard deviation over a particular axis - e.g. I want to compute the
statistics for axis=1 as if the other axes were combined so that in the
On 26 February 2014 22:48, Matthew Brett matthew.br...@gmail.com wrote:
In that case, the OSX instructions could (within the next few months)
be as simple as:
Install python from binary installer at python.org
curl -O https://raw.github.com/pypa/pip/master/contrib/get-pip.py
python
On 26 February 2014 00:35, Daniele Nicolodi dani...@grinta.net wrote:
simpler in my original email has to be read as involving less
operations and thus more efficient, not simpler to understand, indeed it
is already a simple implementation of the definition. What I would like
to know is if
On 25 February 2014 11:08, Daniele Nicolodi dani...@grinta.net wrote:
Hello,
I'm dealing with an instrument that transfers numerical values through
an RS232 port in a custom (?) floating point representation (56 bits, 4
bits exponent and 52 bits significand).
Of course I need to convert
On 24 February 2014 05:21, Nathaniel Smith n...@pobox.com wrote:
I've tentatively rewritten the first section of the PEP to try and
accomplish this framing:
https://github.com/njsmith/numpy/blob/matmul-pep/doc/neps/return-of-revenge-of-matmul-pep.rst
Comments welcome etc.
I've not been
On 24 February 2014 13:26, Daniele Nicolodi dani...@grinta.net wrote:
Hello,
I've noticed that numpy default format for saving data in ascii
representation with np.savetxt() is %.18e. Given that the default
data type for numpy is double and that the resolution of doubles is 15
decimal
On 24 January 2014 22:43, Chris Barker chris.bar...@noaa.gov wrote:
Oscar,
Cool stuff, thanks!
I'm wondering though what the use-case really is.
The use-case is precisely the use-case for dtype='S' on Py2 except
that it also works on Py3.
The P3 text model
(actually the py2 one, too), is
On Wed, Jan 22, 2014 at 05:53:26PM -0800, Chris Barker - NOAA Federal wrote:
On Jan 22, 2014, at 1:13 PM, Oscar Benjamin oscar.j.benja...@gmail.com
wrote:
It's not safe to stop removing the null bytes. This is how numpy determines
the length of the strings in a dtype='S' array
On 23 January 2014 17:42, josef.p...@gmail.com wrote:
On Thu, Jan 23, 2014 at 12:13 PM, josef.p...@gmail.com wrote:
On Thu, Jan 23, 2014 at 11:58 AM, josef.p...@gmail.com wrote:
No, a view doesn't change the memory, it just changes the
interpretation and there shouldn't be any conversion
There have been a few threads discussing the problems of how to do
text with numpy arrays in Python 3.
To make a slightly more concrete proposal, I've implemented a pure
Python ndarray subclass that I believe can consistently handle
text/bytes in Python 3. It is intended to be an illustration
On 23 January 2014 21:51, Chris Barker chris.bar...@noaa.gov wrote:
However, I would prefer latin-1 -- that way you might get garbage for the
non-ascii parts, but it wouldn't raise an exception and it round-trips
through encoding/decoding. And you would have a somewhat more useful subset
--
On 24 January 2014 01:09, Chris Barker chris.bar...@noaa.gov wrote:
On Thu, Jan 23, 2014 at 4:02 PM, Oscar Benjamin oscar.j.benja...@gmail.com
wrote:
On 23 January 2014 21:51, Chris Barker chris.bar...@noaa.gov wrote:
However, I would prefer latin-1 -- that way you might get garbage
On Tue, Jan 21, 2014 at 06:54:33PM -0700, Andrew Collette wrote:
Hi Chris,
it looks from here:
http://www.hdfgroup.org/HDF5/doc/ADGuide/WhatsNew180.html
that HDF uses utf-8 for unicode strings -- so you _could_ roundtrip with a
lot of calls to encode/decode -- which could be pretty
On Wed, Jan 22, 2014 at 12:07:28PM -0800, Chris Barker wrote:
On Wed, Jan 22, 2014 at 2:46 AM, Oscar Benjamin
oscar.j.benja...@gmail.comwrote:
BTW, as much as the fixed-width 'S' dtype doesn't really work for str in
Python 3 it's also a poor fit for bytes since it strips trailing nulls
On Mon, Jan 20, 2014 at 04:12:20PM -0700, Charles R Harris wrote:
On Mon, Jan 20, 2014 at 3:58 PM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Mon, Jan 20, 2014 at 3:35 PM, Nathaniel Smith n...@pobox.com wrote:
On Mon, Jan 20, 2014 at 10:28 PM, Charles R Harris
On Tue, Jan 21, 2014 at 07:34:19AM +0100, Dr. Leo wrote:
Hi,
I would like to write something like:
In [25]: iterable=((i, i**2) for i in range(10))
In [26]: a=np.fromiter(iterable, int32)
---
ValueError
On Tue, Jan 21, 2014 at 11:41:30AM +, Nathaniel Smith wrote:
On 21 Jan 2014 11:13, Oscar Benjamin oscar.j.benja...@gmail.com wrote:
If the Numpy array would manage the buffers itself then that per string
memory
overhead would be eliminated in exchange for an 8 byte pointer and at
least
On Tue, Jan 21, 2014 at 06:55:29AM -0700, Charles R Harris wrote:
Well, that's open for discussion. The problem is to have something that is
both compact (latin-1) and interoperates transparently with python 3
strings (utf-8). A latin-1 type would be easier to implement and would
probably be
On Fri, Jan 17, 2014 at 02:30:19PM -0800, Chris Barker wrote:
Folks,
I've been blathering away on the related threads a lot -- sorry if it's too
much. It's gotten a bit tangled up, so I thought I'd start a new one to
address this one question (i.e. dont bring up genfromtext here):
Would
On Mon, Jan 20, 2014 at 10:00:55AM -0500, Aldcroft, Thomas wrote:
On Mon, Jan 20, 2014 at 5:11 AM, Oscar Benjamin
oscar.j.benja...@gmail.comwrote:
How significant are the performance issues? Does anyone really use numpy
for
this kind of text handling? If you really are operating
On Jan 20, 2014 5:21 PM, Charles R Harris charlesr.har...@gmail.com
wrote:
On Mon, Jan 20, 2014 at 10:12 AM, Aldcroft, Thomas
aldcr...@head.cfa.harvard.edu wrote:
On Mon, Jan 20, 2014 at 10:40 AM, Oscar Benjamin
oscar.j.benja...@gmail.com wrote:
On Mon, Jan 20, 2014 at 10:00:55AM -0500
On Jan 20, 2014 8:35 PM, Charles R Harris charlesr.har...@gmail.com
wrote:
I think we may want something like PEP 393. The S datatype may be the
wrong place to look, we might want a modification of U instead so as to
transparently get the benefit of python strings.
The approach taken in PEP 393
On Fri, Jan 17, 2014 at 10:59:27AM +, Pauli Virtanen wrote:
Julian Taylor jtaylor.debian at googlemail.com writes:
[clip]
- inconvenience in dealing with strings in python 3.
bytes are not strings in python3 which means ascii data is either a byte
array which can be inconvenient to
On Fri, Jan 17, 2014 at 02:10:19PM +0100, Julian Taylor wrote:
On Fri, Jan 17, 2014 at 1:44 PM, Oscar Benjamin
oscar.j.benja...@gmail.comwrote:
On Fri, Jan 17, 2014 at 10:59:27AM +, Pauli Virtanen wrote:
Julian Taylor jtaylor.debian at googlemail.com writes:
[clip
On Fri, Jan 17, 2014 at 03:12:32PM +0100, Julian Taylor wrote:
On Fri, Jan 17, 2014 at 2:40 PM, Oscar Benjamin
oscar.j.benja...@gmail.comwrote:
On Fri, Jan 17, 2014 at 02:10:19PM +0100, Julian Taylor wrote:
no, the right solution is to add an encoding argument.
Its a 4 line patch
On Fri, Jan 17, 2014 at 10:58:25AM -0500, josef.p...@gmail.com wrote:
On Fri, Jan 17, 2014 at 10:26 AM, Oscar Benjamin
oscar.j.benja...@gmail.com wrote:
On Fri, Jan 17, 2014 at 03:12:32PM +0100, Julian Taylor wrote:
You don't show how you created the file. I think that in your case
On Wed, Jan 15, 2014 at 11:40:58AM -0800, Chris Barker wrote:
On Wed, Jan 15, 2014 at 9:57 AM, Charles R Harris charlesr.har...@gmail.com
wrote:
There was a discussion of this long ago and UCS-4 was chosen as the numpy
standard. There are just too many complications that arise in
On 15 January 2014 12:38, Julian Taylor jtaylor.deb...@googlemail.com wrote:
On 01/15/2014 11:25 AM, Daπid wrote:
On 15 January 2014 11:12, Hedieh Ebrahimi hedieh.ebrah...@amphos21.com
mailto:hedieh.ebrah...@amphos21.com wrote:
I try to print my fileContent array after I read it and it
On 19 December 2013 16:49, Andrei Rozanski and...@ruivo.org wrote:
Sorry if I was not clear enough.
The SO question is alike what I want. However, in my problem, Im not sure if
there will be only one occurence.
What I do expect is:
Given one array (big one), to retrieve indexes for query
On 19 December 2013 12:51, rootspin and...@ruivo.org wrote:
Hello,
Need some help in searching arrays (Im new to numpy)
Is it possible to search a array, using another array considering
order/sequence?
x = np.array([1,2,3,4,5,6], np.int32)
y = np.array([1,4,3,2,6,5], np.int32)
query=
On 6 December 2013 20:09, Chris Barker chris.bar...@noaa.gov wrote:
2. in the absence of statistics, can we do an experiment by putting one
wheel up on PyPi which contains SSE3 instructions, for python 3.3 I propose,
and seeing for how many (if any) users this goes wrong?
sounds good -- it
On 14 November 2013 17:19, David Cournapeau courn...@gmail.com wrote:
On Thu, Nov 14, 2013 at 4:45 PM, Charles Waldman char...@crunch.io wrote:
Can you post the raw data? It seems like there are just a couple of bad
sizes, I'd like to know more precisely what these are.
Indeed. Several of
42 matches
Mail list logo