Re: Coding conventions for class names

2007-04-26 Thread Michael Hoffman
Kay Schluehr wrote: > What happens when an enthusiast re-implements a stdlib module e.g. > decimal s.t. it becomes a builtin module? Will the stdlib module serve > as a wrapper to conform the current API or will the builtin module > conform to the current interface. Well, the best example is prob

Re: Coding conventions for class names

2007-04-26 Thread Martin v. Löwis
Kay Schluehr schrieb: > set, int, float, list, object,... > > Don't see any of the basic types following the capitalized word > convention for classes covered by PEP 08. These aren't classes, they are types. PEP 8 doesn't specify any convention for types; it is common to either apply the convent

Re: Coding conventions for class names

2007-04-26 Thread Kay Schluehr
On 25 Apr., 12:32, Michael Hoffman <[EMAIL PROTECTED]> wrote: > Kay Schluehr wrote: > > My question is: does anyone actually follow guidelines here > > Yes. > > > and if yes > > which ones and are they resonable ( e.g. stable with regard to > > refactoring etc. )? > > All of them that I know of. Wh

Re: Coding conventions for class names

2007-04-25 Thread Michael Hoffman
Marc 'BlackJack' Rintsch wrote: > In <[EMAIL PROTECTED]>, Kay Schluehr > wrote: > >> set, int, float, list, object,... >> >> Don't see any of the basic types following the capitalized word >> convention for classes covered by PEP 08. This does not hold only for >> __builtins__ in the strict sense

Re: Coding conventions for class names

2007-04-25 Thread Michael Hoffman
Kay Schluehr wrote: > My question is: does anyone actually follow guidelines here Yes. > and if yes > which ones and are they resonable ( e.g. stable with regard to > refactoring etc. )? All of them that I know of. What does it mean to be "stable with regard to refactoring etc."? -- Michael H

Re: Coding conventions for class names

2007-04-25 Thread Marc 'BlackJack' Rintsch
In <[EMAIL PROTECTED]>, Kay Schluehr wrote: > set, int, float, list, object,... > > Don't see any of the basic types following the capitalized word > convention for classes covered by PEP 08. This does not hold only for > __builtins__ in the strict sense but also for types defined in builtin > mo

Coding conventions for class names

2007-04-25 Thread Kay Schluehr
set, int, float, list, object,... Don't see any of the basic types following the capitalized word convention for classes covered by PEP 08. This does not hold only for __builtins__ in the strict sense but also for types defined in builtin modules like datetime. My question is: does anyone actuall