On Mon, 2008-07-07 at 13:34 -0400, Benji York wrote:
> On Mon, Jul 7, 2008 at 1:28 PM, Tim Cook <[EMAIL PROTECTED]> wrote:
> >
> > Okay, the problem is defined but it really isn't a solution for me.
> > It seems that Zope has defined 'description' as a keyword not allowed in
> > schema definitions
On Mon, Jul 7, 2008 at 2:25 PM, Tim Cook <[EMAIL PROTECTED]> wrote:
> Okay. But before I do that. Is my approach to initializing an instance
> correct or is the problem the way I handled the keywords?
...
>for n,v in kw.items():
>setattr(self,n,v)
There are people who like th
On Mon, 2008-07-07 at 13:34 -0400, Benji York wrote:
> On Mon, Jul 7, 2008 at 1:28 PM, Tim Cook <[EMAIL PROTECTED]> wrote:
> >
> > Okay, the problem is defined but it really isn't a solution for me.
> > It seems that Zope has defined 'description' as a keyword not allowed in
> > schema definitions
On Mon, Jul 7, 2008 at 1:28 PM, Tim Cook <[EMAIL PROTECTED]> wrote:
>
> Okay, the problem is defined but it really isn't a solution for me.
> It seems that Zope has defined 'description' as a keyword not allowed in
> schema definitions.
That's rather odd. Can you construct a small example (say, a
Okay, the problem is defined but it really isn't a solution for me.
It seems that Zope has defined 'description' as a keyword not allowed in
schema definitions.
The WrongType error occurs in validation because Zope thinks it is the
'description' of the attribute and not the attribute itself. T
On Mon, 2008-07-07 at 13:58 -0300, Tim Cook wrote:
> ... and I've learned a lot thanks to you patience.
>
> On Mon, 2008-07-07 at 12:41 -0300, Tim Cook wrote:
> > I've been Googling for a script I can run against all of my source to
> > test characters for unicode just in case there are more of t
