Philipp von Weitershausen wrote at 2006-9-4 16:49 +0200:
>I for one prefer exceptions over manual error handling. And I prefer
>straight-forward APIs over unnecessarily complicated constructs.
But you probably would not prefer if these "straight-forward APIs"
were continously changing.
I prefer a slightly suboptimal stable API over one that is
optimized in each version in a non backward compatible way.
I do not want to say that this is happening in Zope3 land.
I do not yet use Zope3 in earnest and see what is happening
more from the mailing list than from my own experience.
>> So, for me, it would be great if developers would take more time to
>> weigh up the "what does this new feature or refactoring bring" against
>> the "how much of a PITA is it going to be for everyone else to relearn
I like new features but often could not see the gain of refactorings.
Many refactorings in Zope 2 land were just silly, e.g. whitespace
refactoring such as:
from X.Y.Z import a, b, c
from X.Y.Z import a
from X.Y.Z import b
from X.Y.Z import c
I do see the gain of moving out general purpose functions from
"zope.app" into "zope". But, I would do it in a backward
compatible way -- even when "zope.app" then contains quite
a few trivial packages redirecting to the relocated packages.
Zope3-dev mailing list