[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 s

[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

[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

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 sentenc

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

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