hi,
it seems that http://buildbot.zope.org/ seems to be pretty borked.
iirc benji is taking care of the build master and other people are
maintaining the slaves.
in case we don't have enough slave maintainers, lovely systems would
be happy to provide a slave for linux 2.6 and make sure
On 2007-08-24 07:55:08 +0200, Jodok Batlogg [EMAIL PROTECTED] said:
hi christian,
it seems like your recent changes to support skins in xmlrpc views =20
introduced some troubles.
we spent several hours to debug not working xmlrpc views and finally =20
found that nailing the zope.traversing
Hi
I'm implementing the getValidationErrors thingy right now and once
again stumbled upon the ValidationErrors. Their __repr__ is all but
useful.
For instance TooSmall:
TooSmall(8, 10)
8 10
Another sort of related issue is that you only get the __doc__ string
when calling the .doc()
Aha! After reading this message now I finally understand the reason I
can't browse svn.zope.org with my Nokia N800[1] anymore.
This used to be quite useful since I could read lots of *.txt documents
from zope3 and related projects just before sleeping. I wish I could do
it again.
I've setup an
Cc: zope3-dev zope3-dev
Betreff: [Zope3-dev] skin support for xmlrpc
hi christian,
it seems like your recent changes to support skins in xmlrpc
views introduced some troubles.
we spent several hours to debug not working xmlrpc views and
finally found that nailing the zope.traversing
On 24 Aug 2007, at 07:05 , Andreas Jung wrote:
--On 24. August 2007 02:37:01 +0200 Philipp von Weitershausen
[EMAIL PROTECTED] wrote:
http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/
maintaining-so
ftware.txt
Thanks for writing this excellent guide. However I am personally
Christian Zagrodnick wrote:
I'm implementing the getValidationErrors thingy right now and once again
stumbled upon the ValidationErrors. Their __repr__ is all but useful.
For instance TooSmall:
TooSmall(8, 10)
8 10
Another sort of related issue is that you only get the __doc__ string
when
Christian,
I understand the use cases and I see how using the skin concept for
XMLRPC is tempting. But couldn't you have done this is in an extra
package? This way, you wouldn't have had to touch at least three
different zope.* packages *and* risk breaking stuff for the others with
something
On Friday 24 August 2007 04:00, Christian Zagrodnick wrote:
What should we do about this?
Well, I personally think for a programming API the error message is okay. The
__repr__ could be better though, I agree.
For forms and other UI components, this text should be at most used for a
default.
Am Freitag, den 24.08.2007, 09:05 -0400 schrieb Stephan Richter:
On Friday 24 August 2007 04:00, Christian Zagrodnick wrote:
What should we do about this?
Well, I personally think for a programming API the error message is okay. The
__repr__ could be better though, I agree.
For forms
On Friday 24 August 2007 09:10, Christian Theune wrote:
For forms and other UI components, this text should be at most used for a
default. z3c.form allows you to easily customize those error messages,
for example.
As long as this doesn't mean that we don't provide reasonable values in
the
On Thursday 23 August 2007 20:37, Philipp von Weitershausen wrote:
I would like to get your comments on it. No matter what this evolves to,
I wouldn't mind eventually seeing it set in stone with your blessings,
so that the checkin police can use it as the highway code to issue
tickets to
On 24 Aug 2007, at 15:25 , Stephan Richter wrote:
On Thursday 23 August 2007 20:37, Philipp von Weitershausen wrote:
I would like to get your comments on it. No matter what this
evolves to,
I wouldn't mind eventually seeing it set in stone with your
blessings,
so that the checkin police can
On Aug 24, 2007, at 4:00 AM, Christian Zagrodnick wrote:
Hi
I'm implementing the getValidationErrors thingy right now and once
again stumbled upon the ValidationErrors. Their __repr__ is all but
useful.
For instance TooSmall:
TooSmall(8, 10)
8 10
Another sort of related issue is
On Friday 24 August 2007 09:52, Jim Fulton wrote:
What should we do about this?
While better __str__s or __reprs__ is often nice, as a general
principal, errors should be displayed through adaptation -- basically
views.
They are, but the text is used by the views to show the error. This
On Aug 24, 2007, at 5:07 AM, Lorenzo Gil Sanchez wrote:
Aha! After reading this message now I finally understand the reason I
can't browse svn.zope.org with my Nokia N800[1] anymore.
I don't see what one has to do with the other.
This used to be quite useful since I could read lots of *.txt
On Friday 24 August 2007 09:34, Philipp von Weitershausen wrote:
Well, this may sound harsh, but I see some appeal in actually forcing
a particular coding-style on everybody.
That's not harsh. That's the point of a coding style. :-) The long-term
benefits are greater.
It's soo late for
--On 24. August 2007 09:25:14 -0400 Stephan Richter
[EMAIL PROTECTED] wrote:
On Thursday 23 August 2007 20:37, Philipp von Weitershausen wrote:
I would like to get your comments on it. No matter what this evolves to,
I wouldn't mind eventually seeing it set in stone with your blessings,
so
On 8/24/07, Andreas Jung [EMAIL PROTECTED] wrote:
We should not be too pendantic when it comes to coding styles. I assume
that most contributors to Zope 3 or Zope components know how to write code
the Zope 3 way.
As the community grows, this is an increasingly poor assumption.
Different
--On 24. August 2007 12:21:24 -0400 Fred Drake [EMAIL PROTECTED] wrote:
On 8/24/07, Andreas Jung [EMAIL PROTECTED] wrote:
We should not be too pendantic when it comes to coding styles. I assume
that most contributors to Zope 3 or Zope components know how to write
code the Zope 3 way.
As
On 8/24/07, Stephan Richter [EMAIL PROTECTED] wrote:
That's not harsh. That's the point of a coding style. :-) The long-term
benefits are greater.
Agreed!
But if you prefer consistency, then we really should be staying with the Zope
3 style guide,
This, of course, all depends on the answer
On 8/24/07, Andreas Jung [EMAIL PROTECTED] wrote:
My statement was focused on discussions like camel case vs. underscores.
Such discussions are basically academic.
Agreed.
In real life when you develop
software for different companies or projects it is hard to switch your
personal coding
On Friday 24 August 2007 12:21, Fred Drake wrote:
I don't think that's what this is. This is a document describing how
things /are/ done in the Zope 3 repository. That's helpful both as it
stands and as a foundation for a document on how things should be
going forward.
This has nothing to
On Friday 24 August 2007 12:59, Fred Drake wrote:
But let's be pragmatic at some point...
Right. Adopt *one* style, due to the long-term benefits, and don't change
it.
I totally agree. It was the main reason for the original style guide for Zope
3; but you both were around when we worked
On Friday 24 August 2007 12:55, Fred Drake wrote:
I don't really care whether the style is the classic Zope 3 style or
PEP 8, as long as it never changes.
He he, except that the ``zc`` namespace started using PEP 8. ;-) I am pretty
sure the vast majority of code in the repos is classic Zope 3.
On 8/24/07, Stephan Richter [EMAIL PROTECTED] wrote:
He he, except that the ``zc`` namespace started using PEP 8. ;-) I am pretty
sure the vast majority of code in the repos is classic Zope 3. ``zope``,
``z3c`` (for most parts), and ``lovely`` all follow Zope 3.
Even worse, the ``zc``
--On 24. August 2007 19:27:23 +0200 Dieter Maurer [EMAIL PROTECTED]
wrote:
I find it very stupid to prescribe whilespace rules and
Whitespace rules have a major impact on the readability of code.
Readability is a major point when we talk of code quality. Readable code
does not make code
Andreas Jung wrote at 2007-8-24 19:35 +0200:
...
Whitespace rules have a major impact on the readability of code.
Readability is a major point when we talk of code quality. Readable code
does not make code automatically but good code has to be readable.
Lots of whitespace does not make the code
On 24 Aug 2007, at 19:27 , Dieter Maurer wrote:
Philipp von Weitershausen wrote at 2007-8-24 15:34 +0200:
...
This and other aspects are things I don't particularly love about
PEP8 either, but I value consistency over my personal preferences.
I do honor other people's
decisions though, and
On 24 Aug 2007, at 19:55 , Dieter Maurer wrote:
Andreas Jung wrote at 2007-8-24 19:35 +0200:
...
Whitespace rules have a major impact on the readability of code.
Readability is a major point when we talk of code quality.
Readable code
does not make code automatically but good code has to be
On 8/24/07, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
it's a matter of taste and that's hard to argue about.
No, that's easy to argue about, it's just not productive. That's the
problem. :-)
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Chaos is the score upon which reality
--On 24. August 2007 19:55:35 +0200 Dieter Maurer [EMAIL PROTECTED]
wrote:
Andreas Jung wrote at 2007-8-24 19:35 +0200:
...
Whitespace rules have a major impact on the readability of code.
Readability is a major point when we talk of code quality. Readable code
does not make code
There are three branches of zope.file:
branches/0.1
branches/0.2
trunk
There were reasons for so many, but I don't remember what all of them
are; there were at least two aspects to this split.
One aspect that differs is the use of ZODB blobs. I think another is
the location of the result
33 matches
Mail list logo
