-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Fred Drake wrote:
> On 9/5/06, Dieter Maurer <[EMAIL PROTECTED]> wrote:
>> When I remember right, then I read an important sentence in the
>> Python style guide -- something along the lines: "This is a guide:
>> you should follow it but there are occasions when you may not do so with
>> good reasons."
> 
> I don't know if this means you agree or not.
> 
> I don't think this paragraph really applies to this discussion.  Jim
> suggested that we change the Z3 style guide, and I'm suggesting that

I think this is an important point:

> that's counter-productive.  Clearly, existing code isn't affected
> immediately, and APIs can't be changed anyway.

But changing APIs is what we do, and what we probably have to do, and
probably keep doing. However, I think, we need to get much more careful
with it and maybe we can try harder keeping existing APIs around,
although we find better ways to spell/implement/dress them.

Christian

- --
gocept gmbh & co. kg - forsterstra├če 29 - 06112 halle/saale - germany
www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE/cuhdUt9X/gknwIRAs2BAKDUOmJwPUtpeCmaZwba/hY32/HdcACgwH+N
LXmTosSKo5BU+HkmdZK7H34=
=m4s9
-----END PGP SIGNATURE-----
_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to