On Sat, Jan 7, 2017 at 2:52 PM, Charles R Harris
wrote:
>
>
> On Fri, Jan 6, 2017 at 6:37 PM, wrote:
>
>>
>>
>>
>> On Fri, Jan 6, 2017 at 8:28 PM, Ralf Gommers
>> wrote:
>>
>>>
>>>
>>> On Sat, Jan 7, 2017 at 2:21 PM, CJ Carey
>>> wrote:
>>>
On Fri, Jan 6, 2017 at 6:19 PM, Ralf Gommer
On Fri, Jan 6, 2017 at 6:37 PM, wrote:
>
>
>
> On Fri, Jan 6, 2017 at 8:28 PM, Ralf Gommers
> wrote:
>
>>
>>
>> On Sat, Jan 7, 2017 at 2:21 PM, CJ Carey
>> wrote:
>>
>>>
>>> On Fri, Jan 6, 2017 at 6:19 PM, Ralf Gommers
>>> wrote:
>>>
This sounds like a reasonable idea. Timeline could be s
On Fri, Jan 6, 2017 at 8:28 PM, Ralf Gommers wrote:
>
>
> On Sat, Jan 7, 2017 at 2:21 PM, CJ Carey
> wrote:
>
>>
>> On Fri, Jan 6, 2017 at 6:19 PM, Ralf Gommers
>> wrote:
>>
>>> This sounds like a reasonable idea. Timeline could be something like:
>>>
>>> 1. Now: create new package, deprecate n
On Sat, Jan 7, 2017 at 2:21 PM, CJ Carey wrote:
>
> On Fri, Jan 6, 2017 at 6:19 PM, Ralf Gommers
> wrote:
>
>> This sounds like a reasonable idea. Timeline could be something like:
>>
>> 1. Now: create new package, deprecate np.matrix in docs.
>> 2. In say 1.5 years: start issuing visible deprec
On Fri, Jan 6, 2017 at 6:19 PM, Ralf Gommers wrote:
> This sounds like a reasonable idea. Timeline could be something like:
>
> 1. Now: create new package, deprecate np.matrix in docs.
> 2. In say 1.5 years: start issuing visible deprecation warnings in numpy
> 3. After 2020: remove matrix from n
On Wed, Jan 4, 2017 at 9:07 AM, Bryan Van de Ven
wrote:
> There's a good chance that bokeh.charts will be split off into a
> separately distributed package as well. Hopefully being a much smaller,
> pure Python project makes it a more accessible target for anyone interested
> in maintaining it, a
