On Wed, Aug 14, 2013 at 10:35 AM, Mark Wiebe wrote:
Hi Mark, great to have you thinking (and coding) about this!
>> - Marc also commented that making datetime64 time-zone naive would be
>> "the easy way"
>
> I've experimented a little bit with one possibility in this direction within
> dynd. Bas
On Wed, Aug 14, 2013 at 9:00 AM, Chris Barker - NOAA Federal <
chris.bar...@noaa.gov> wrote:
> On Tue, Aug 13, 2013 at 5:54 PM, Charles R Harris
> wrote:
> > I wish it were. It seems unreasonably difficult to get constructive
> > feedback. Chris is pretty much the only one making the attempt and
On Tue, Aug 13, 2013 at 5:54 PM, Charles R Harris
wrote:
> I wish it were. It seems unreasonably difficult to get constructive
> feedback. Chris is pretty much the only one making the attempt and that
> discussion petered out.
well, Nathaniel Smith chimed in, and Mark Weibe commented a bit (as he
I wish it were. It seems unreasonably difficult to get constructive
feedback. Chris is pretty much the only one making the attempt and that
discussion petered out. I don't use datetime64 much myself, probably what
we need is a developer who does use that facility. Any volunteers?
Chuck
On Tue, A
Hi,
On Mon, Aug 12, 2013 at 4:16 PM, Chris Barker - NOAA Federal
wrote:
> On Mon, Aug 12, 2013 at 3:14 PM, Charles R Harris
> wrote:
>
>>> > Datetime64 will not be modified in this release.
>>>
>>> I now there is neither the time nor the will for all that it needs,
>>> but please, please, please
On Mon, Aug 12, 2013 at 3:14 PM, Charles R Harris
wrote:
>> > Datetime64 will not be modified in this release.
>>
>> I now there is neither the time nor the will for all that it needs,
>> but please, please, please, can we yank out the broken timezone
>> handling at least?
>>
>> https://github.co
On Mon, Aug 12, 2013 at 4:05 PM, Chris Barker - NOAA Federal <
chris.bar...@noaa.gov> wrote:
> On Mon, Aug 12, 2013 at 2:41 PM, Charles R Harris
> wrote:
>
> > Datetime64 will not be modified in this release.
>
> I now there is neither the time nor the will for all that it needs,
> but please, pl
On Mon, Aug 12, 2013 at 2:41 PM, Charles R Harris
wrote:
> Datetime64 will not be modified in this release.
I now there is neither the time nor the will for all that it needs,
but please, please, please, can we yank out the broken timezone
handling at least?
https://github.com/numpy/numpy/issue
Hi All,
I think we are about ready to start on the 1.8 release. There are a few
things left to do, but there are PR's for most of them. There are a couple
of issues that I think need discussion.
1. Should diagonal return a view in this release or the next?
2. Should multiple field selection
