On 12.05.19 14:58, Charles R Harris wrote:
> Hi All,
>
> NumPy currently distinguishes between release and development versions
> when running tests. Is there a good reason to continue this practice? I
> ask, because with the last pytest release it would be convenient to
> always include `pytest.i
Hi,
We understand that it can be burden, of course a larger binary is bad
but that bad usually also comes with good, like better performance or
more features.
How much of a burden is it and where is the line between I need twice as
long to download it which is just annoying and I cannot use it any
On 08.03.2018 17:20, Charles R Harris wrote:
>
>
> On Thu, Mar 8, 2018 at 2:52 AM, Gregor Thalhammer
> mailto:gregor.thalham...@gmail.com>> wrote:
>
>
> Hi,
>
> long time ago I wrote a wrapper to to use optimised and parallelized
> math functions from Intels vector math library
>
On 06.11.2017 11:10, Ralf Gommers wrote:
>
>
> On Mon, Nov 6, 2017 at 7:25 AM, Charles R Harris
> mailto:charlesr.har...@gmail.com>> wrote:
>
> Hi All,
>
> Thought I'd toss this out there. I'm tending towards better sooner
> than later in dropping Python 2.7 support as we are starti
On 21.07.2017 08:52, Ralf Gommers wrote:
> Hi all,
>
> It has been well over a year since we put together the governance
> structure and steering council
> (https://docs.scipy.org/doc/numpy-dev/dev/governance/people.html#governance-people).
> We haven't reviewed the people on the steering council
On 25.06.2017 18:45, Stefan van der Walt wrote:
> Hi Chuck
>
> On Sun, Jun 25, 2017, at 09:32, Charles R Harris wrote:
>> The boolean binary '-' operator was deprecated back in NumPy 1.9 and
>> changed to an error in 1.13. This caused a number of failures in
>> downstream projects. The choices now
On 12.05.2017 16:28, Jens Jørgen Mortensen wrote:
> Den 11-05-2017 kl. 03:48 skrev Charles R Harris:
>> Hi All,
>>
>> I'm please to announce the NumPy 1.13.0rc1 release. This release
>> supports Python 2.7 and 3.4-3.6 and contains many new features. It is
>> one of the most ambitious releases in th
On 26.04.2017 19:08, Robert Kern wrote:
> On Wed, Apr 26, 2017 at 2:15 AM, Julian Taylor
> mailto:jtaylor.deb...@googlemail.com>>
> wrote:
>
>> Indeed,
>> Most of this discussion is irrelevant to numpy.
>> Numpy only really deals with the in memory storage of s
On 26.04.2017 03:55, josef.p...@gmail.com wrote:
> On Tue, Apr 25, 2017 at 9:27 PM, Charles R Harris
> wrote:
>>
>>
>> On Tue, Apr 25, 2017 at 5:50 PM, Robert Kern wrote:
>>>
>>> On Tue, Apr 25, 2017 at 3:47 PM, Chris Barker - NOAA Federal
>>> wrote:
>>>
> Presumably you're getting byte stri
On 20.04.2017 20:59, Anne Archibald wrote:
> On Thu, Apr 20, 2017 at 8:17 PM Julian Taylor
> mailto:jtaylor.deb...@googlemail.com>>
> wrote:
>
> I probably have formulated my goal with the proposal a bit better, I am
> not very interested in a repetition of whic
On 20.04.2017 20:53, Robert Kern wrote:
> On Thu, Apr 20, 2017 at 6:15 AM, Julian Taylor
> mailto:jtaylor.deb...@googlemail.com>>
> wrote:
>
>> Do you have comments on how to go forward, in particular in regards to
>> new dtype vs modify np.unicode?
>
> Can we
, Julian Taylor wrote:
> Hello,
> As you probably know numpy does not deal well with strings in Python3.
> The np.string type is actually zero terminated bytes and not a string.
> In Python2 this happened to work out as it treats bytes and strings the
> same way. But in Python3 this type
Hello,
As you probably know numpy does not deal well with strings in Python3.
The np.string type is actually zero terminated bytes and not a string.
In Python2 this happened to work out as it treats bytes and strings the
same way. But in Python3 this type is pretty hard to work with as each
time yo
hi,
we need to deprecate the NPY_CHAR typenumber [0] in order to enable us
to add new core dtypes without adding ugly hacks to our ABI.
Technically the typenumber was deprecated way back in 1.6 when it
accidentally broke our ABI. But due to lack of time f2py never got
updated to actually follow thr
On 15.04.2017 16:30, Julian Taylor wrote:
> On 15.04.2017 16:17, Marten van Kerkwijk wrote:
>> Hi All,
>>
>> I think Nathaniel had a good summary. My own 2¢ are mostly about the
>> burden of supporting python2. I have only recently attempted to make
>> changes in t
On 15.04.2017 16:17, Marten van Kerkwijk wrote:
> Hi All,
>
> I think Nathaniel had a good summary. My own 2¢ are mostly about the
> burden of supporting python2. I have only recently attempted to make
> changes in the C codebase of numpy and one of the reasons I found this
> more than a little da
On 15.04.2017 02:19, Charles R Harris wrote:
> Hi All,
>
> It may be early to discuss dropping support for Python 2.7, but there is
> a disturbance in the force that suggests that it might be worth looking
> forward to the year 2020 when Python itself will drop support for 2.7.
> There is also a w
hi,
It has been very very long overdue but we finally have an attempt of
making our text io functions actually use text IO instead of bytes IO.
This means genfromtxt, loadtxt, fromregex and savetxt should support
unicode input files of any python supported encoding and universal newlines.
This is t
On 31.03.2017 16:07, Julian Taylor wrote:
> On 31.03.2017 15:51, Nathaniel Smith wrote:
>> On Mar 31, 2017 1:15 AM, "Ralf Gommers" > <mailto:ralf.gomm...@gmail.com>> wrote:
>>
>>
>>
>> On Mon, Mar 27, 2017 at 11:42 PM, Ra
On 31.03.2017 15:51, Nathaniel Smith wrote:
> On Mar 31, 2017 1:15 AM, "Ralf Gommers" <mailto:ralf.gomm...@gmail.com>> wrote:
>
>
>
> On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers
> mailto:ralf.gomm...@gmail.com>> wrote:
>
>
>
I have two ideas under one big important topic: make numpy python3
compatible.
The first fits pretty well with the grant size and nobody wants to do it
for free:
- fix our text IO functions under python3 and support multiple
encodings, not only latin1.
Reasonably simple to do, slap encoding argume
21 matches
Mail list logo
