>>> The tests pass on my machine, but I see that the TravisCI builds are
>>> giving assertion fails (on my own test) with python 3.3 and 3.5 of the
>>> form:
>>> > assert_almost_equal
>>> > TypeError: Cannot cast array data from dtype('complex128') to
>>> dtype('float64') according to the rule 'saf
>> > assert_almost_equal
>> > TypeError: Cannot cast array data from dtype('complex128') to
>> dtype('float64') according to the rule 'safe'
>>
>>
>
> Hi Peter, that error is unrelated to assert_almost_equal. What happens is
> that when you pass in a complex argument `fp` to your modified
> `compil
On Tue, Dec 22, 2015 at 7:42 AM, Ralf Gommers
wrote:
>
>
> On Tue, Dec 22, 2015 at 12:55 AM, Peter Creasey <
> p.e.creasey...@googlemail.com> wrote:
>
>> Hi all,
>> I submitted a PR (#6872) for using complex numbers in np.lib.interp.
>>
>> The tests pass on my machine, but I see that the TravisCI
On Tue, Dec 22, 2015 at 12:55 AM, Peter Creasey <
p.e.creasey...@googlemail.com> wrote:
> Hi all,
> I submitted a PR (#6872) for using complex numbers in np.lib.interp.
>
> The tests pass on my machine, but I see that the TravisCI builds are
> giving assertion fails (on my own test) with python 3.
Hi all,
I submitted a PR (#6872) for using complex numbers in np.lib.interp.
The tests pass on my machine, but I see that the TravisCI builds are
giving assertion fails (on my own test) with python 3.3 and 3.5 of the
form:
> assert_almost_equal
> TypeError: Cannot cast array data from dtype('compl
