[Zope-dev] standard_error_message no longer used in Zope 2.12?

[Jens Vagelpohl]

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


On Apr 24, 2009, at 16:35 , Chris Withers wrote:

> Jens Vagelpohl wrote:
>> Sorry Chris, but that's exactly the method you use every single time.
>> You complain very loudly and expect others to come to your help and
>> fix stuff without doing any debugging yourself, even though you are
>> perfectly capable of doing so.
>
> What? So it's out of order of me to ask for whoever made this change  
> to
> actually speak up and say what they did?

You're not out of order for speaking up. Not at all. However, you're  
the only person with a deep Zope knowledge who expects that other  
people do the debugging for him.

The whole assumption that a specific committer somehow remembers that  
a specific code change he or she made breaks whatever you find to be  
broken is faulty. It's very easy to work on one end of Zope and  
inadvertently break something at the other end that may not be covered  
well enough by tests. You cannot just expect that someone will speak  
up and say "oh yeah, I broke standard_error_message". But you can  
provide some serious help by doing debugging and pinpointing the  
issue. The chance that someone will remember what they did and why  
once you describe the underlying cause will be a lot larger. And they  
will most likely fix it for you then.

jens


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAknx0MIACgkQRAx5nvEhZLLycQCfTxmNPT9PEiNPiuTOC1YoAd0B
7EcAoJGX20wW3E2zWKbDaDKxeBCwx7fg
=3689
-----END PGP SIGNATURE-----