[SciPy-dev] New release on Monday
schofield at ftw.at
Sun Dec 11 16:43:10 CST 2005
On 11/12/2005, at 9:55 PM, Ed Schofield wrote:
> On 11/12/2005, at 8:53 AM, Travis Oliphant wrote:
>> I'm going to make a new release of scipy core on Monday evening (U.S.
>> Mountain Time)
>> unless I hear from anyone. I'll probably post new Windows
>> binaries of
>> full scipy
>> at that point as well.
>> Now's a good time for any bug-reports or outstanding issues.
> Is there any chance of including type checking for this release for
> unsafe in-place operations? Several people supported the idea in
> the thread [In-place operators and casting] a few weeks ago. In
> summary, the existing behaviour would still be achievable with an
> explicit cast:
> >>> my_int_array += my_float_array.astype(int)
Actually, I may as well stick my neck out and argue that another (the
last remaining?) example of unsafe casting behaviour
>>> my_int_array = 1.5
ought to change too eventually. I'd argue for a TypeError here
also. The current behaviour would still be achievable with an
explicit cast like
>>> my_int_array = int(1.5).
with a bonus of easier readability. I'd guess that the performance
impact of a type check would be small, given the overhead anyway of
setting an individual array element from Python. But I'll run some
benchmark tests to verify this...
More information about the Scipy-dev