The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
mhammond
- Windows DevelopmentMode penalty in CMFCore.DirectoryView,
[Accepted] http://www.zope.org/Collectors/CMF/366
Pending / Deferred Issues
Hi,
I'll just offer one alternative solution for disussion, which could
avoid reverting all the changes we made.
Kapil Thangavelu wrote:
We believe that these recent changes have introduced implicit magic into
a standard Zope3 api to fit Zope2 acquisition. There should be an
explicit separate
Maurits van Rees, on 2007-03-29:
I see the same problem in a Plone Product of mine (eXtremeManagement)
where bookings added after the DST get listed a day earlier in one
page template. When I add a booking somewhere in November (I can
choose the booking date) that one gets listed fine again.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maurits van Rees wrote:
Stefan H. Holek, on 2007-03-28:
Much fun to be had with daylight-saving, eh?
FWIW, I have double-checked the system time, timezone, and locale
settings on the machine running the nightlies, and everything appears
to
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
I would say that all of Acquisition is dark implicit magic and something
I expect when developing in Zope 2. When using Zope 3 concepts in Zope 2
I also expect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sidnei da Silva wrote:
On 3/29/07, Tres Seaver [EMAIL PROTECTED] wrote:
The consensus is that the Right Thing(TM) is to switch over to using
pytz, which is updated regularly when the politically-defined DST rules
change; I'm not sure anyone has
Sidnei da Silva wrote:
On 3/29/07, Tres Seaver [EMAIL PROTECTED] wrote:
The cheeseshop shows a pytz-2007d version:
http://cheeseshop.python.org/pypi/pytz
I was refering to the version included in Zope.
That's because we're using a stupid vendor import instead of simply
requiring it as
Tres Seaver wrote:
I'm not sure what impact that would have for the already-converted code
which used to use the API. I can see value both in leaving it
converted, as showing the Zope3-ish way, as well as in reverting some or
all of it. For instance, perhaps we should consider reverting just
Philipp von Weitershausen wrote at 2007-3-28 08:16 +0200:
...
What makes you think you can make that assumption? This is Zope 2 all
over again, where things just have to be there. That won't help
making things more flexible.
Hiding exceptions (or avoiding them at all costs) might be seen as
