[SciPy-dev] Suppressing of numpy __mul__, __div__ etc

Dmitrey tmp50@ukr....
Mon Dec 14 15:03:37 CST 2009


It seems I was wrong - the issue doesn't matter for matrices, so we could use something like __exclude_ndarray_operations__ . If there will be no collective opinion of numpy developers in term of several hours, please don't mind me to commit the changes, it would be very important to have quarterly release of FuncDesigner being free of the bug.
Regards, D.

P.S. scipy.org server is down for now.


--- Исходное сообщение ---
От кого: Charles R Harris <charlesr.harris@gmail.com>
Кому: SciPy Developers List <scipy-dev@scipy.org>
Дата: Dec 14, 2009  22:01:53
Тема: Re: [SciPy-dev] Suppressing of numpy __mul__, __div__ etc

2009/12/14 Dmitrey <tmp50@ukr.net>
 > 
 > >
 > >
 > > --- Исходное сообщение ---
 > > От кого: Charles R Harris <charlesr.harris@gmail.com>
 > > Кому: SciPy Developers List <scipy-dev@scipy.org>
 > > Дата: 14 декабря, 20:26:12
 > > Тема: Re: [SciPy-dev] Suppressing of numpy __mul__, __div__ etc
 > >
 > > 2009/12/14 Dmitrey <tmp50@ukr.net>
 > >
 > > >
 > > >
 > > > --- Исходное сообщение ---
 > > > От кого: Charles R Harris <charlesr.harris@gmail.com>
 > > > Кому: SciPy Developers List <scipy-dev@scipy.org>
 > > > Дата: 14 декабря, 20:06:46
 > > > Тема: Re: [SciPy-dev] Suppressing of numpy __mul__, __div__ etc
 > > >
 > > > 2009/12/14 Dmitrey <tmp50@ukr.net>
 > > >
 > > > > I don't think the field name '__do_not_treat_as_scalar__ ' is a good
 > > > > choice. At first, it will be unclear what it is used for, at 2nd, some
 > > > users
 > > > > / classes, that certainly are not scalars with overloaded __rdiv__ etc
 > > > > sometimes will prefer numpy __div__ method to be used.
 > > > > As for me, I would prefer something like '__use_self_operators = True'
 > > or
 > > >
 > > > > '__use_numpy_operations = False' or
 > > '__involve_self_overloaded_methods__
 > > > =
 > > > > True'.
 > > > > I have to release FuncDesigner tomorrow (to keep my quarterly schedule)
 > >
 > > > so
 > > > > please inform me ASAP which name do you finally choose.
 > > > > Thank you in advance, D.
 > > > >
 > > > >
 > > > I think it should have numpy or ndarray in the name somewhere to indicate
 > >
 > > > that it is numpy specific. Hmm <looks in thesaurus>, maybe,
 > > >
 > > > __supercede_ndarray__,
 > > > __disallow_ndarray__,
 > > > __deny_ndarray__,
 > > > __reject_ndarray__,
 > > > __refuse_ndarray__,
 > > > __exclude_ndarray__,
 > > > __reject_ndarray__, ...
 > > >
 > > > My preference among those would be __deny_ndarray__.
 > > >
 > > >
 > > > But isn't the issue present with numpy matrices or scipy.sparse matrices
 > > as
 > > > well?
 > > > So I guess instead of ndarray another word should be used.
 > > >
 > >
 > > __has_precedence__
 > > __is_prior__
 > >
 > > Chuck
 > >
 > >
 > > I guess some numpy developers should choose the final name in numpy IRC
 > > channel and inform the list (ASAP) about their collective (and hence final)
 > > decision. I'm not skilled in English quite enough, but so short names seems
 > > too uninformative to me, they will be not used too often so I guess more
 > > informative should be preferred.
 > >
 > 
 > I don't think we should rush this. I'm waiting for more people to weigh in
 > or offer different solutions.
 > 
 > Chuck
 > 
 > 




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/scipy-dev/attachments/20091214/7073b2b5/attachment.html 


More information about the SciPy-Dev mailing list