Re: [Numpy-discussion] Canopy and Anaconda

2013-04-10 Thread David Cournapeau
Hi Colin, Please ask Canopy question on the corresponding Enthought list, or Anaconda questions on the corresponding channel at continuum. This Mailing List is for discussion about NumPy itself, David On Thu, Apr 11, 2013 at 1:43 AM, Colin J. Williams wrote: > Are CANOPY and Anaconda intende

Re: [Numpy-discussion] Time Zones and datetime64

2013-04-10 Thread Riccardo De Maria
Daniele Nicolodi grinta.net> writes: > > On 10/04/2013 18:55, Riccardo De Maria wrote: > > The library should handle correctly leap seconds, otherwise using unix time > > as a floating point number is already sufficient for many applications. > > Please define what you mean by "handle correctly

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Alan G Isaac
On 4/10/2013 10:25 AM, Dmitrey wrote: > Refactoring is mere impossible See Nathaniel's suggestion. Alan Isaac ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Time Zones and datetime64

2013-04-10 Thread Chris Barker - NOAA Federal
On Wed, Apr 10, 2013 at 9:55 AM, Riccardo De Maria wrote: > The library should handle correctly leap seconds, otherwise using unix time > as a floating point number is already sufficient for many applications. well, we could have used floating point in datetime64, but integers have their advanta

Re: [Numpy-discussion] Time Zones and datetime64

2013-04-10 Thread Daniele Nicolodi
On 10/04/2013 18:55, Riccardo De Maria wrote: > The library should handle correctly leap seconds, otherwise using unix time > as a floating point number is already sufficient for many applications. Please define what you mean by "handle correctly leap seconds". As leap seconds are not predictable

Re: [Numpy-discussion] Time Zones and datetime64

2013-04-10 Thread Riccardo De Maria
Thanks for the effort. I think one should assume UTC when the time zones are not explicit. The library should handle correctly leap seconds, otherwise using unix time as a floating point number is already sufficient for many applications. Did you have a look to http://cr.yp.to/libtai.html? Ric

Re: [Numpy-discussion] Time Zones and datetime64

2013-04-10 Thread Chris Barker - NOAA Federal
On Wed, Apr 10, 2013 at 4:21 AM, Colin J. Williams wrote: > On Mon, Apr 8, 2013 at 12:24 PM, Chris Barker - NOAA Federal >> Recent discussion has made it clear that the timezone handling in the >> current (numpy1.7) version of datetime64 is broken. Below is a >> discussion of some possible solutio

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Dmitrey
--- Исходное сообщение --- От кого: "Alan G Isaac" Дата: 10 апреля 2013, 15:12:07 On 4/10/2013 3:31 AM, Robert Kern wrote: > You cannot use objects that do not have a valid __eq__() (as in, > returns boolean True if and only if they are to be considered > equivalent for the purpose of dictiona

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Nathaniel Smith
An easy solution to all of this is to use a dict-like object that matches keys based on object identity while ignoring __hash__ and __eq__ entirely, e.g.: https://bitbucket.org/pypy/pypy/src/2f51f2142f7b/lib_pypy/identity_dict.py#cl-9 -n On Wed, Apr 10, 2013 at 10:45 AM, Sebastian Berg wrote: >

Re: [Numpy-discussion] Import error while freezing with cxfreeze

2013-04-10 Thread V. Armando Solé
Hello, On 10/04/2013 11:13, Anand Gadiyar wrote: On Friday, April 5, 2013, Anand Gadiyar wrote: Hi all, I have a small program that uses numpy and scipy. I ran into a couple of errors while trying to use cxfreeze to create a windows executable. I'm run

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Alan G Isaac
On 4/10/2013 3:31 AM, Robert Kern wrote: > You cannot use objects that do not have a valid __eq__() (as in, > returns boolean True if and only if they are to be considered > equivalent for the purpose of dictionary lookup, otherwise returns > False) as dictionary keys. Your oofun object still viola

Re: [Numpy-discussion] Time Zones and datetime64

2013-04-10 Thread Colin J. Williams
On 09/04/2013 5:46 PM, Mark Wiebe wrote: On Mon, Apr 8, 2013 at 12:24 PM, Chris Barker - NOAA Federal wrote: Recent discussion has made it clear that the timezone handling in

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Sebastian Berg
On Wed, 2013-04-10 at 11:45 +0200, Sebastian Berg wrote: > On Wed, 2013-04-10 at 11:54 +0300, Dmitrey wrote: > > On 04/10/2013 10:31 AM, Robert Kern wrote: > > > You think comparing tracked bug counts across different projects > > > means anything? That's adorable. I admire your diligence at > > >

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Sebastian Berg
On Wed, 2013-04-10 at 11:45 +0200, Sebastian Berg wrote: > On Wed, 2013-04-10 at 11:54 +0300, Dmitrey wrote: > > On 04/10/2013 10:31 AM, Robert Kern wrote: > > This is all good and nice, but Robert is still right. For dictionaries > to work predictable you need to ensure two things. > > First:

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Sebastian Berg
On Wed, 2013-04-10 at 11:54 +0300, Dmitrey wrote: > On 04/10/2013 10:31 AM, Robert Kern wrote: > > You think comparing tracked bug counts across different projects > > means anything? That's adorable. I admire your diligence at > > addressing the bugs that you do acknowledge. That was never in > >

Re: [Numpy-discussion] Import error while freezing with cxfreeze

2013-04-10 Thread Anand Gadiyar
Hi Brad, On Fri, Apr 5, 2013 at 8:33 PM, Bradley M. Froehle wrote: > Hi Anand, > > On Friday, April 5, 2013, Anand Gadiyar wrote: > >> Hi all, >> >> I have a small program that uses numpy and scipy. I ran into a couple of >> errors while trying to use cxfreeze to create a windows executable. >> >

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Dmitrey
On 04/10/2013 10:31 AM, Robert Kern wrote: You think comparing tracked bug counts across different projects means anything? That's adorable. I admire your diligence at addressing the bugs that you do acknowledge. That was never in question. But refusing to acknowledge a bug is not the same thin

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Nathaniel Smith
On 10 Apr 2013 08:01, "Dmitrey" wrote: > > --- Исходное сообщение --- > От кого: "Robert Kern" > Дата: 9 апреля 2013, 14:29:43 > >> On Tue, Apr 9, 2013 at 4:15 PM, Dmitrey wrote: >> > >> > >> > --- Исходное сообщение --- >> > От кого: "Robert Kern" >> > Дата: 16 марта 2013, 22:15:07 >> > >> > O

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Robert Kern
On Wed, Apr 10, 2013 at 1:06 PM, Nathaniel Smith wrote: > This kind of personal attack is never appropriate for this list. Please > stop. My apologies. I will stop. -- Robert Kern ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mai

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Robert Kern
On Wed, Apr 10, 2013 at 12:30 PM, Dmitrey wrote: > > > --- Исходное сообщение --- > От кого: "Robert Kern" > Дата: 9 апреля 2013, 14:29:43 >> Well, it's your software. You are free to make it as buggy as you wish, I >> guess. > > Yes, and that's why each time I get a bugreport I immediately star

Re: [Numpy-discussion] OpenOpt Suite release 0.45

2013-04-10 Thread Dmitrey
> --- Исходное сообщение --- От кого: "Robert Kern" Дата: 9 апреля 2013, 14:29:43 On Tue, Apr 9, 2013 at 4:15 PM, Dmitrey < tm...@ukr.net > wrote: > > > --- Исходное сообщение --- > От кого: "Robert Kern" < robert.k...@gmail.com > > Дата: 16 марта 2013, 22:15:07 > > On Sat, Mar 16, 2013 at