I think the bug was referring to the fact that some types have duplicate names *explicitly* containing the letter "c" -- as in >>> repr(N.intc) '<type 'numpy.int32'>'
Is this supposed to be consistent naming scheme (i.e. any C type "<T>" is accessible as "N.<T>c") ? Then c float-type should consequently be named N.floatc . Futhermore, sometimes the "c" appears first, as in: >>> N.clongfloat <type 'numpy.complex192'> >>> N.clongdouble <type 'numpy.complex192'> ... and what does the "p" stand for in >>> N.intp <type 'numpy.int32'> Otherwise please elaborate why some names like "intc" exist, and which exactly those are !? (BTW, the name "N.single" is there to make FORTRAN people feel more comfortable - right ?) Thanks, -Sebastian > > > On Wed, Mar 19, 2008 at 5:16 PM, Matthieu Brucher > <[EMAIL PROTECTED]> wrote: > > For the not blocker bugs, I think that #420 should be closed : float32 is > > the the C float type, isn't it ? > > > > Matthieu > > > > 2008/3/13, Jarrod Millman <[EMAIL PROTECTED]>: > > > > > Hello, > > > > > > I am sure that everyone has noticed that 1.0.5 hasn't been released > > > yet. The main issue is that when I was getting ready to tag the > > > release I noticed that the buildbot had a few failing tests: > > > http://buildbot.scipy.org/waterfall?show_events=false > > > > > > Stefan van der Walt added tickets for the failures: > > > http://projects.scipy.org/scipy/numpy/ticket/683 > > > http://projects.scipy.org/scipy/numpy/ticket/684 > > > http://projects.scipy.org/scipy/numpy/ticket/686 > > > And Chuck Harris fixed ticket #683 with in minutes (thanks!). The > > > others are still open. > > > > > > Stefan and I also triaged the remaining tickets--closing several and > > > turning others in to release blockers: > > > > > http://scipy.org/scipy/numpy/query?status=new&severity=blocker&milestone=1.0.5&order=priority > > > > > > I think that it is especially important that we spend some time trying > > > to make the 1.0.5 release rock solid. There are several important > > > changes in the trunk so I really hope we can get these tickets > > > resolved ASAP. I need everyone's help getting this release out. If > > > you can help work on any of the open release blockers, please try to > > > close them over the weekend. If you have any ideas about the tickets > > > but aren't exactly sure how to resolve them please post a message to > > > the list or add a comment to the ticket. > > > > > > I will be traveling over the weekend, so I may be off-line until Monday. > > > > > > Thanks, > > > > > > -- > > > Jarrod Millman > > > Computational Infrastructure for Research Labs > > > 10 Giannini Hall, UC Berkeley > > > phone: 510.643.4014 > > > http://cirl.berkeley.edu/ > > > _______________________________________________ > > > Numpy-discussion mailing list > > > Numpy-discussion@scipy.org > > > http://projects.scipy.org/mailman/listinfo/numpy-discussion > > > > > > > > > > > -- > > French PhD student > > Website : http://matthieu-brucher.developpez.com/ > > Blogs : http://matt.eifelle.com and http://blog.developpez.com/?blog=92 > > LinkedIn : http://www.linkedin.com/in/matthieubrucher > > _______________________________________________ > > Numpy-discussion mailing list > > Numpy-discussion@scipy.org > > http://projects.scipy.org/mailman/listinfo/numpy-discussion > > > > > _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
