On Mon, Dec 21, 2015 at 7:42 PM, Ian Henriksen <
insertinterestingnameh...@gmail.com> wrote:
> Also, am I correct that these are win64 builds only? Anyone know if it
>> would be easy to add win32?
>>
>
> It'd be really easy to add 32 bit builds. The main reason I didn't was
> because appveyor only
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.
On Mon, Dec 21, 2015 at 11:11 PM, Chris Barker
wrote:
> On Fri, Dec 18, 2015 at 1:51 PM, Ralf Gommers
>>
>> +1 from me. Despite the number of downloads still being high, I don't
>> think there's too much value in these binaries anymore.
>>
>
> If there are a lot of downloads, then there is value.
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
On Fri, Dec 18, 2015 at 1:51 PM, Ralf Gommers
>
> +1 from me. Despite the number of downloads still being high, I don't
> think there's too much value in these binaries anymore.
>
If there are a lot of downloads, then there is value. At least until we
have binary wheels on PyPi.
What's up with th
Why, why, why is it not the empty string. you can't actually fill an `S2`
type with such a string, hence one must convert masked string arrays to a
list of strings to use it. That is pathetic.
Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scip
>
> The Python 3 build runs much faster than the Python 2. You can close and
>> reopen my testing PR to check what happens if you enable the numpy project.
>
>
I'm not sure why this is the case. MSVC 2015 is generally better about a
lot of things, but it's
surprising that the speed difference is so
>
> Also, am I correct that these are win64 builds only? Anyone know if it
> would be easy to add win32?
>
It'd be really easy to add 32 bit builds. The main reason I didn't was
because appveyor only
gives one concurrent build job for free, and I didn't want to slow things
down too much. I can get