On Tue, Feb 14, 2012 at 6:25 PM, Travis Oliphant wrote:
>
> On Feb 14, 2012, at 3:32 AM, David Cournapeau wrote:
>
>> Hi Travis,
>>
>> It is great that some resources can be spent to have people paid to
>> work on NumPy. Thank you for making that happen.
>>
>> I am slightly confused about roadmaps
On Tue, Feb 14, 2012 at 12:25 PM, Travis Oliphant wrote:
>
> There is a mailing list for numfocus that you can sign up for if you would
> like to be part of those discussions. Let me know if you would like more
> information about that.
I would like more information about (as would many oth
On Tue, Feb 14, 2012 at 1:03 AM, Travis Oliphant wrote:
>
>Mostly I'm happy with the changes (after a cursory review). As I
> expected, there are some real improvements.Of course, I haven't looked
> at the changes that occur when the scalar being used does not fit in the
> range of t
On Feb 14, 2012, at 3:32 AM, David Cournapeau wrote:
> Hi Travis,
>
> It is great that some resources can be spent to have people paid to
> work on NumPy. Thank you for making that happen.
>
> I am slightly confused about roadmaps for numpy 1.8 and 2.0. This
> needs discussion on the ML, and ou
Hi Travis,
It is great that some resources can be spent to have people paid to
work on NumPy. Thank you for making that happen.
I am slightly confused about roadmaps for numpy 1.8 and 2.0. This
needs discussion on the ML, and our release manager currently is Ralf
- he is the one who ultimately de
For reference, here is the table that shows the actual changes between 1.5.1
and 1.6.1 at least on 64-bit platforms in terms of type-casting. I updated the
comparison code to throw out changes that are just "spelling differences" (i.e.
where 1.6.1 chooses to create an output dtype with an 'L' c
