Re: [Zope3-dev] Re: TALES PathExpr doesn't call old style classes

2006-05-25 Thread Philipp von Weitershausen
Dieter Maurer wrote:
> Philipp von Weitershausen wrote at 2006-5-24 18:16 +0200:
>> ...
>> Yup. We could think about this for some future release cycle, though.
>> I'd very much be in favour of making nocall: the default and introduce
>> something like call:. Then sniffing for callableness wouldn't be necessary.
> 
> You are aware how many templates you would break?

Of course, we'd have to introduce it in a way that wouldn't break all
the existing templates at once. There are numerous possibilities to do
that, all of which can be discussed in due time when this becomes an
issue. Right now my focus is getting Zope 2.10 in a beta status.

Philipp

___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] Re: TALES PathExpr doesn't call old style classes

2006-05-25 Thread Dieter Maurer
Philipp von Weitershausen wrote at 2006-5-24 18:16 +0200:
> ...
>Yup. We could think about this for some future release cycle, though.
>I'd very much be in favour of making nocall: the default and introduce
>something like call:. Then sniffing for callableness wouldn't be necessary.

You are aware how many templates you would break?


-- 
Dieter
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



RE: [Zope3-dev] Re: [Checkins] SVN: Zope3/trunk/src/zope/formlib/Bugfix zope.formlib

2006-05-25 Thread dev
Hi Gary

[...]
> On May 25, 2006, at 12:17 PM, Roger Ineichen wrote:
> ...
> 
> Looks good to me for 3.3 also.

Ok, the bugfix is merged to the trunk.

> > +Note that a EditForm can't make use of a get_rendered method. The
> > get_rendered
> > +method does only set initial values.
> 
> This sentence got me closer to understanding what you want, at least.

I guess we have to think about this concept another time.
Perhaps it make sense to add a setRenderedValue concept
to the formlib. This well know field method could also make 
sense at a form level and offer a post process hook for set
values on initialized widgets. This could be useful for 
convert form.request values before they get collected by
the field getInputValue method.

Regards
Roger Ineichen
_
END OF MESSAGE

> Thanks
> 
> Gary
> ___
> Zope3-dev mailing list
> Zope3-dev@zope.org
> Unsub: 
> http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch
> 
> 

___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] Re: [Checkins] SVN: Zope3/trunk/src/zope/formlib/ Bugfix zope.formlib

2006-05-25 Thread Gary Poster


On May 25, 2006, at 12:17 PM, Roger Ineichen wrote:
...

Looks good to me for 3.3 also.


+Note that a EditForm can't make use of a get_rendered method. The  
get_rendered

+method does only set initial values.


This sentence got me closer to understanding what you want, at least.

Thanks

Gary
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] pkg_resources or pkgutil?

2006-05-25 Thread Philipp von Weitershausen
Zope3's zope/__init__.py now contains:

  try:
  # Declare this a namespace package if pkg_resources is available.
  import pkg_resources
  pkg_resources.declare_namespace('zope')
  except ImportError:
  pass

where as Zope2's zope/__init__.py contains:

  from pkgutil import extend_path
  __path__ = extend_path(__path__, __name__)

I think they do pretty much the same thing (but I could be mistaken).
Are they interchangeable? If not, are they compatible so that we just
add both ways to both files? If they're not compatible, which one should
we use in the future?

Philipp

___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] weird problem with pytz+DC

2006-05-25 Thread Adam Groszer
Hi there,

I've run into the following problem when trying to use zc.datetimewidget
in my app: IZopeDublinCore.modified value is a datetime, but it is
having a tzinfo(0) as I check it, instead of pytz.utc. That's weird,
because timeannotators.py sets it as
dc.modified = datetime.now(pytz.utc)
But somehow it gets unpickled again as with tzinfo(0). That's not bad,
but comparing tzinfo(0) with pytz.utc fails.

Am I doing something wrong? Anybody noticed that already?

-- 
Best regards,
 Adam  mailto:[EMAIL PROTECTED]
--
Quote of the day:
To believe with certainty, we must begin with doubting. 
- Stanislaus I 

___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com