On Fri, Nov 20, 2015 at 6:29 PM, CJ Carey wrote:
> The short answer is: "kind of".
>
> These two Github issues explain what's going on more in-depth:
> https://github.com/scipy/scipy/issues/3995
> https://github.com/scipy/scipy/issues/4239
>
Thanks, I didn't pay attention to those issues, or on
The short answer is: "kind of".
These two Github issues explain what's going on more in-depth:
https://github.com/scipy/scipy/issues/3995
https://github.com/scipy/scipy/issues/4239
As for the warning only showing once, that's Python's default behavior for
warnings: http://stackoverflow.com/q/2266
On Fri, Nov 20, 2015 at 2:00 PM, Charles R Harris wrote:
>
>
> On Fri, Nov 20, 2015 at 1:42 PM, Orion Poplawski
> wrote:
>
>> On 11/12/2015 02:11 PM, Charles R Harris wrote:
>> > Hi All,
>> >
>> > I am pleased to announce the release of Numpy 1.10.2rc1. This release
>> should
>> > fix the proble
On Fri, Nov 20, 2015 at 1:42 PM, Orion Poplawski
wrote:
> On 11/12/2015 02:11 PM, Charles R Harris wrote:
> > Hi All,
> >
> > I am pleased to announce the release of Numpy 1.10.2rc1. This release
> should
> > fix the problems exposed in 1.10.1, which is not to say there are no
> remaining
> > pro
On 11/12/2015 02:11 PM, Charles R Harris wrote:
> Hi All,
>
> I am pleased to announce the release of Numpy 1.10.2rc1. This release should
> fix the problems exposed in 1.10.1, which is not to say there are no remaining
> problems. Please test this thoroughly, exspecially if you experienced proble
Is this intentional?
>>> exog
<50x5 sparse matrix of type ''
with 50 stored elements in Compressed Sparse Column format>
>>> np.asarray(exog)
array(<50x5 sparse matrix of type ''
with 50 stored elements in Compressed Sparse Column format>, dtype=object)
I'm just a newbie who thought to use the
