Hi , I am Mohammed Faisal Anees , a Computer Science student at IIIT- Hyderabad. I was going though the ideas page and I found "Improve Numpy datetime functionality" really interesting , and it suits my experience as I have a considerable(hopefully !!) amount of experience in C/C++, and Python . Right now I am going through the link suggested by you and the codebase. Thanks
On Sat, Mar 1, 2014 at 6:42 AM, faisal anees < mohammedfaisal.anees@students.iiit.ac.in> wrote:
I am Mohammed Faisal Anees , a Computer Science student at IIIT- Hyderabad. I was going though the ideas page and I found "Improve Numpy datetime functionality" really interesting ,
It's great to have the interest! One trick is that I dont hink there is a consensus on what needs to be done to "improve datetime". One thing that does need to be done is cleaning up time zone handling -- and I think we ALMOST have consensus on how to do that (at least the quick fix part). Take a look for threads on this list in the last year about "datetime64" and this ticket: https://github.com/numpy/numpy/issues/3388 (and search for other datetime64 tickets...) Note that we are hoping to fix that for 1.9 -- anyone have a time scale for that? Too soon for GSoC? -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov
On Mon, Mar 3, 2014 at 6:38 PM, Chris Barker <chris.barker@noaa.gov> wrote:
On Sat, Mar 1, 2014 at 6:42 AM, faisal anees < mohammedfaisal.anees@students.iiit.ac.in> wrote:
I am Mohammed Faisal Anees , a Computer Science student at IIIT- Hyderabad. I was going though the ideas page and I found "Improve Numpy datetime functionality" really interesting ,
It's great to have the interest!
One trick is that I dont hink there is a consensus on what needs to be done to "improve datetime".
One thing that does need to be done is cleaning up time zone handling -- and I think we ALMOST have consensus on how to do that (at least the quick fix part).
Take a look for threads on this list in the last year about "datetime64" and this ticket:
https://github.com/numpy/numpy/issues/3388
(and search for other datetime64 tickets...)
Note that we are hoping to fix that for 1.9 -- anyone have a time scale for that? Too soon for GSoC?
Yes too soon and no, unlikely to happen given that no one volunteered yet. So seeing a solid GSoC proposal would be good. Ralf
participants (3)
-
Chris Barker -
faisal anees -
Ralf Gommers