On Sun, 16 Sep 2007 10:17:18 -0400, Colin J. Williams wrote:
> Marc 'BlackJack' Rintsch wrote:
>
>> `getFoo()` is discouraged by PEP 8. […]
>
> Perhaps PEP 8 needs rethinking. I prefer getFoo().
Yeah, *your* preference is a very good reason to rethink PEP 8… ;-)
Ciao,
Marc 'BlackJack'
On 9/16/07, Colin J. Williams <[EMAIL PROTECTED]> wrote:
>
> Marc 'BlackJack' Rintsch wrote:
> > On Thu, 06 Sep 2007 09:00:02 +0200, Stefan Arentz wrote:
> >
> >> What I find really frustrating in Python (combined with usually bad
> >> documentation) is that many people have different styles. The m
Marc 'BlackJack' Rintsch wrote:
> On Thu, 06 Sep 2007 09:00:02 +0200, Stefan Arentz wrote:
>
>> What I find really frustrating in Python (combined with usually bad
>> documentation) is that many people have different styles. The most
>> frustratinng being getFoo() vs .foo, vs get_foo().
>
> `getF
Stefan Arentz a écrit :
> Bruno Desthuilliers <[EMAIL PROTECTED]> writes:
>
> ...
>
>> The problem with Java is that it makes it very painfull to bridge two
>> APIs together, while Python usually makes it a breeze (easy
>> delegation, no dumb-ass psycho-rigid type system). So Java's solution
>> (
Marc 'BlackJack' Rintsch <[EMAIL PROTECTED]> writes:
> On Thu, 06 Sep 2007 09:00:02 +0200, Stefan Arentz wrote:
>
> > What I find really frustrating in Python (combined with usually bad
> > documentation) is that many people have different styles. The most
> > frustratinng being getFoo() vs .foo,
On Thu, 06 Sep 2007 09:00:02 +0200, Stefan Arentz wrote:
> What I find really frustrating in Python (combined with usually bad
> documentation) is that many people have different styles. The most
> frustratinng being getFoo() vs .foo, vs get_foo().
`getFoo()` is discouraged by PEP 8. You don't h
Bruno Desthuilliers <[EMAIL PROTECTED]> writes:
...
> The problem with Java is that it makes it very painfull to bridge two
> APIs together, while Python usually makes it a breeze (easy
> delegation, no dumb-ass psycho-rigid type system). So Java's solution
> (hyper-formalization) isn't necessary
Martin Marcher a écrit :
> Hello,
>
> having worked quite a bit with python in the last months (some Java
> before, and some C++ before that) I was very impressed by an idea the
> Java people had.
>
> Explanation: the JSRs define how to implement certain services and or
> features in Java so that
On Aug 30, 12:10 am, "Martin Marcher" <[EMAIL PROTECTED]>
wrote:
[snip!]
>
> My idea was to define "Python Implementation Guidelines" (PIGs) that
> specify a problem formalize it enough so that implementations are
> interchangeable (in this example create a module that has an
> "authenticate(usern
Hello,
On 30 Aug 2007 07:14:25 GMT, Marc 'BlackJack' Rintsch <[EMAIL PROTECTED]> wrote:
> On Thu, 30 Aug 2007 07:10:47 +0200, Martin Marcher wrote:
>
> > Does that sound like a good idea or would that be over formalization?
>
> Sounds like over engineering/formalization to me.
> You are aware of t
On Thu, 30 Aug 2007 07:10:47 +0200, Martin Marcher wrote:
> My idea was to define "Python Implementation Guidelines" (PIGs) that
> specify a problem formalize it enough so that implementations are
> interchangeable (in this example create a module that has an
> "authenticate(username, password)" me
On Thu, 30 Aug 2007 07:10:47 +0200, Martin Marcher wrote:
> Does that sound like a good idea or would that be over formalization?
Sounds like over engineering/formalization to me.
You are aware of the Python Enhancement Proposals (PEPs)?
Is something like the `Python Database API Specification
Hello,
having worked quite a bit with python in the last months (some Java
before, and some C++ before that) I was very impressed by an idea the
Java people had.
Explanation: the JSRs define how to implement certain services and or
features in Java so that they can be reused. I haven't found such
13 matches
Mail list logo
