On Thu, Jun 5, 2014 at 1:32 PM, Kyle Mandli wrote:
> In the past I know that we have simply gathered in a circle and discussed
> which works as well. Whatever the case, if someone could volunteer to
> "lead" the discussion
>
It's my experience that a really good facilitator could make all the
On Thu, Jun 5, 2014 at 3:24 PM, David Cournapeau wrote:
> On Thu, Jun 5, 2014 at 2:51 PM, Charles R Harris
> wrote:
>> On Thu, Jun 5, 2014 at 6:40 AM, David Cournapeau
>> wrote:
>>> IMO, what is needed the most is refactoring the internal to extract the
>>> Python C API low level from the rest o
On Thu, Jun 5, 2014 at 3:36 AM, Charles R Harris
wrote:
> @nathaniel IIRC, one of the objections to the missing values work was that
> it changed the underlying array object by adding a couple of variables to
> the structure. I'm willing to do that sort of thing, but it would be good to
> have gen
On 05.06.2014 11:13, Daπid wrote:
> pyFFTW provides a drop-in replacement for Numpy and Scipy's fftw:
>
> https://hgomersall.github.io/pyFFTW/pyfftw/interfaces/interfaces.html
Sure. But if you want use multi-threading and the wisdom mechanisms, you
have to take care of it yourself. You didn't ha
Hi Kyle
Kyle Mandli writes:
> The BoF format would be up to those who would lead
> the discussion, a couple of ideas used in the past include picking out a
> few of the lead devs to be on a panel and have a Q&A type of session or an
> open Q&A with perhaps audience guided list of topics.
Unfortu
It sounds like there is a lot to discuss come July and I am sure there will
be others "willing" to voice their opinions as well. The primary goal in
all of this would be to have a constructive discussion concerning the
future of NumPy, do you guys have a feeling for what might be the most
effectiv
On Thu, Jun 5, 2014 at 2:51 PM, Charles R Harris
wrote:
>
>
>
> On Thu, Jun 5, 2014 at 6:40 AM, David Cournapeau
> wrote:
>
>>
>>
>>
>> On Thu, Jun 5, 2014 at 3:36 AM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>>
>>>
>>>
>>>
>>> On Wed, Jun 4, 2014 at 7:29 PM, Travis Oliphant
>>>
On Thu, Jun 5, 2014 at 2:29 AM, Travis Oliphant wrote:
> At some point there *will* be a NumPy 2.0. What features go into NumPy
> 2.0, how much backward compatibility is provided, and how much porting is
> needed to move your code from NumPy 1.X to NumPy 2.X is the real user
> question --- not w
On Thu, Jun 5, 2014 at 6:40 AM, David Cournapeau wrote:
>
>
>
> On Thu, Jun 5, 2014 at 3:36 AM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>>
>>
>>
>> On Wed, Jun 4, 2014 at 7:29 PM, Travis Oliphant
>> wrote:
>>
>>> Believe me, I'm all for incremental changes if it is actually poss
On Thu, Jun 5, 2014 at 8:40 AM, David Cournapeau wrote:
>
>
>
> On Thu, Jun 5, 2014 at 3:36 AM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>>
>>
>>
>> On Wed, Jun 4, 2014 at 7:29 PM, Travis Oliphant
>> wrote:
>>
>>> Believe me, I'm all for incremental changes if it is actually poss
On Thu, Jun 5, 2014 at 8:58 AM, Todd wrote:
>
> On 5 Jun 2014 14:28, "David Cournapeau" wrote:
> >
> >
> >
> >
> > On Thu, Jun 5, 2014 at 9:44 AM, Todd wrote:
> >>
> >>
> >> On 5 Jun 2014 02:57, "Nathaniel Smith" wrote:
> >> >
> >> > On Wed, Jun 4, 2014 at 7:18 AM, Travis Oliphant
> wrote:
>
On Thu, Jun 5, 2014 at 1:58 PM, Todd wrote:
>
> On 5 Jun 2014 14:28, "David Cournapeau" wrote:
>>
>> There has been discussions about integrating numpy a long time ago (can't
>> find a reference right now), and the consensus was that this was possible in
>> its current shape nor advisable. The si
On 5 Jun 2014 14:28, "David Cournapeau" wrote:
>
>
>
>
> On Thu, Jun 5, 2014 at 9:44 AM, Todd wrote:
>>
>>
>> On 5 Jun 2014 02:57, "Nathaniel Smith" wrote:
>> >
>> > On Wed, Jun 4, 2014 at 7:18 AM, Travis Oliphant
wrote:
>> > And numpy will be much harder to replace than numeric --
>> > numeric
On Thu, Jun 5, 2014 at 3:36 AM, Charles R Harris
wrote:
>
>
>
> On Wed, Jun 4, 2014 at 7:29 PM, Travis Oliphant
> wrote:
>
>> Believe me, I'm all for incremental changes if it is actually possible
>> and doesn't actually cost more. It's also why I've been silent until now
>> about anything we a
On Thu, Jun 5, 2014 at 9:44 AM, Todd wrote:
>
> On 5 Jun 2014 02:57, "Nathaniel Smith" wrote:
> >
> > On Wed, Jun 4, 2014 at 7:18 AM, Travis Oliphant
> wrote:
> > And numpy will be much harder to replace than numeric --
> > numeric wasn't the most-imported package in the pythonverse ;-).
>
> If
On 4 June 2014 23:34, Alexander Eberspächer
wrote:
> If you feel pyfftw bothers you with too many FFTW details, you may try
> something like https://github.com/aeberspaecher/transparent_pyfftw
> (be careful, it's a hack that has seen only little testing).
>
pyFFTW provides a drop-in replacement
On 5 Jun 2014 02:57, "Nathaniel Smith" wrote:
>
> On Wed, Jun 4, 2014 at 7:18 AM, Travis Oliphant
wrote:
> And numpy will be much harder to replace than numeric --
> numeric wasn't the most-imported package in the pythonverse ;-).
If numpy is really such a core part of python ecosystem, does it
17 matches
Mail list logo
