A Tuesday 02 October 2007, Timothy Hochberg escrigué:
> One approach would be CapWords the superclasses of these that are
> subclassable, but leave the leaf types alone. For example, looking at
> float32 and its bases :
>
>- numpy.generic -> numpy.Generic
>- numpy.number -> numpy.Number
>
A Tuesday 02 October 2007, Robert Kern escrigué:
> Matthew Brett wrote:
> > On 10/2/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
> >> What is a "class" in this case -- with new-style classes, there is
> >> no distinction between types and classes, so I guess they are all
> >> classes, which me
On 10/2/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
>
> Jarrod Millman wrote:
> > I am hoping that most of you agree with the general principle of
> > bringing NumPy and SciPy into compliance with the standard naming
> > conventions.
>
> +1
>
> > 3. When we release NumPy 1.1, we will convert
Matthew Brett wrote:
> On 10/2/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
>> What is a "class" in this case -- with new-style classes, there is no
>> distinction between types and classes, so I guess they are all classes,
>> which means lots of things like:
>>
>> numpy.float32
>>
>> etc. et
On 10/2/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
> Jarrod Millman wrote:
> > I am hoping that most of you agree with the general principle of
> > bringing NumPy and SciPy into compliance with the standard naming
> > conventions.
Excellent plan - and I think it will make the code considera
Jarrod Millman wrote:
> I am hoping that most of you agree with the general principle of
> bringing NumPy and SciPy into compliance with the standard naming
> conventions.
+1
> 3. When we release NumPy 1.1, we will convert all (or almost all)
> class names to CapWords.
What's the backwards-c
Pearu Peterson wrote:
..
> After fixing the class names in tests then how many classes use
> camelcase style in numpy/distutils? How many of them are implementation
.. ^^^
Btw, I meant numpy/scipy here.
Pearu
___
Numpy-dis
On Tue, Oct 02, 2007 at 09:12:43AM +0200, Pearu Peterson wrote:
>
>
> Jarrod Millman wrote:
> > Hello,
> >
> ..
> > Please let me know if you have any major objections to adopting the
> > Python class naming convention.
>
> I don't object.
Me either.
> > 2. Any one adding a new class to NumP
Jarrod Millman wrote:
> Hello,
>
..
> Please let me know if you have any major objections to adopting the
> Python class naming convention.
I don't object.
> Once we have agreed to using CapWords for classes, we will need to
> decide what to do about our existing class names. Obviously, it is
Hello,
NumPy and SciPy should conform with Guido's style guide as closely as possible:
http://www.python.org/dev/peps/pep-0008/
The only serious divergence that I am aware of between the NumPy and
SciPy codebase and the Python recommended standards is in class
naming. According to Guido, class n
10 matches
Mail list logo
