Re: [Zope-dev] I'd lobe to merge the zope3-dev and zope-dev lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4 Oct 2007, at 15:57, Jim Fulton wrote: Any objections? This would basically involve retiring the zope3-dev list and moving zope3 developers to the zope-dev list. Good idea. +1 from me. I'm not on zope3-dev but won't mind additional traffic about topics that I may not care about (yet). And as Andreas says, it's a step closer to getting rid of the Zope 2/3 confusion. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHBeKCRAx5nvEhZLIRAjLnAJ9JIEUNQl0wKOjQP6WeLD7Lxk0lIgCdHtL3 Ybom3qvL7Mo9gW6vd+8wtSo= =tp37 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] I'd lobe to merge the zope3-dev and zope-dev lists
Jim Fulton wrote: Any objections? This would basically involve retiring the zope3-dev list and moving zope3 developers to the zope-dev list. +1 from me :-) Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: I'd lobe to merge the zope3-dev and zope-dev lists
Jim Fulton wrote: This would basically involve retiring the zope3-dev list and moving zope3 developers to the zope-dev list. +1 I sense in my lobes that I'm in favor of this. :) Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Thu Oct 4 12:00:00 2007 UTC to Fri Oct 5 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Oct 4 20:51:55 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008441.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Oct 4 20:53:26 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008442.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Oct 4 20:54:56 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008443.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Oct 4 20:56:26 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008444.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Oct 4 20:57:56 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008445.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Changing DateTime to use pytz
On 10/5/07, Laurence Rowe [EMAIL PROTECTED] wrote: I've tested my patch (datetime.datetime support) against Amos's branch and it applies cleanly and all tests pass. Cool! Are there tests to make sure old pickles still work, or do we know that this is the case for sure? -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Changing DateTime to use pytz
Lennart Regebro wrote:
On 10/5/07, Laurence Rowe [EMAIL PROTECTED] wrote:
I've tested my patch (datetime.datetime support) against Amos's branch
and it applies cleanly and all tests pass.
Cool! Are there tests to make sure old pickles still work, or do we
know that this is the case for sure?
My patch updates the existing test (substituting _millis for _micros):
def testUpgradeOldInstances(self):
# Compare dates that don't have the _micros attribute yet
dt = DateTime('1997/1/1')
dt1 = DateTime('1997/2/2')
del dt._micros
del dt1._micros
self.testCompareOperations(dt, dt1)
If anyone thinks it is important I could an explicit upgrade path for
instances with a _millis attribute too (most current instances I would
assume). _upgrade_old should work fine for them too as they have a time
float _t attribute.
def _upgrade_old(self):
Upgrades a previously pickled DateTime object.
micros = long(math.floor(self._t * 100.0))
self._micros = micros
return micros
Laurence
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Changing DateTime to use pytz
I've tested my patch (datetime.datetime support) against Amos's branch
and it applies cleanly and all tests pass.
It seems though that the new timezones are not used much... doing a
DateTime() gives me DateTime('2007/10/05 14:20:27.204176 GMT+1') (with
my pathc applied too). Looking up tz = d._tzinfo[d.timezone()] gives me
an old style timezone, as _tz is 'GMT+1'.
It would be very useful to be able to get pytz tzinfo for a DateTime
object. It would allow me to return a timezone aware datetime.datetime
from asdatetime().
Ideally the old names should be mapped onto pytz timezones.
Laurence
Laurence Rowe wrote:
I've been working on this too today (well datetime handling anyway).
Please see my patch at https://bugs.launchpad.net/zope2/+bug/149060
Laurence
Amos Latteier wrote:
Hi,
I wanted to let folks know that I've created the amos-datetime-pytz
branch with my changes.
Please let me know when/if you'd like me to merge this to the trunk.
Of course I'm also happy to receive any criticism or comments on the
changes.
Thanks!
-Amos
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Changing DateTime to use pytz
On 10/5/07, Laurence Rowe [EMAIL PROTECTED] wrote:
It seems though that the new timezones are not used much... doing a
DateTime() gives me DateTime('2007/10/05 14:20:27.204176 GMT+1') (with
my pathc applied too). Looking up tz = d._tzinfo[d.timezone()] gives me
an old style timezone, as _tz is 'GMT+1'.
If a the timezone has a name that pytz understands then it uses pytz.
Otherwise it falls back on DateTime's timezone database. The most
common example of when pytz won't be used is with fixed offset
timezones like GMT+1. pytz.common_timezones doesn't doesn't contain
time zones like this. Anyway DateTime handles fixed offset time zones
just fine since there's no daylight savings to deal with.
It would be very useful to be able to get pytz tzinfo for a DateTime
object. It would allow me to return a timezone aware datetime.datetime
from asdatetime().
DateTime instances only store the name of their timezone, not the
timezone object. So when converting to a datetime object I suggest
that you generate a tzinfo object yourself. This shouldn't be too hard
since DateTime is willing to give you a timezone that provides a name,
dst flag, and offset from UTC. See _timezone.info()
Ideally the old names should be mapped onto pytz timezones.
Names that pytz understands use pytz time zone info, regardless of
when the DateTime instance was created. Or maybe you are asking
something else.
Also DateTime supports some abbreviations. For example, 'est' is
mapped to 'US/Eastern'. So old instances that use 'est' as a time zone
should work with pytz. There are probably improvements that can be
made here, but I didn't bother since my goal was to change as little
as possible.
-Amos
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: WSGI2
Jim Fulton wrote: There's work going on to create a second version of WSGI. Last time, we didn't pay much attention until WSGI was a done deal. This time, I think it would be better if we were involved earlier. Unfortunately, I don't have time to pay attention. Does anyone else? I don't. I currently don't know enough about WSGI in the first place to say much that is sensible. I think Tres Seaver, Philipp von Weitershausen and Chris McDonough should volunteer, though. :) Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Changing DateTime to use pytz
On 10/5/07, Laurence Rowe [EMAIL PROTECTED] wrote: If anyone thinks it is important I could an explicit upgrade path for instances with a _millis attribute too (most current instances I would assume). I think the code must work with current instances without modifying them. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Changing DateTime to use pytz
Lennart Regebro wrote: On 10/5/07, Laurence Rowe [EMAIL PROTECTED] wrote: If anyone thinks it is important I could an explicit upgrade path for instances with a _millis attribute too (most current instances I would assume). I think the code must work with current instances without modifying them. All the tests still pass if I comment out the assignment: def _upgrade_old(self): Upgrades a previously pickled DateTime object. micros = long(math.floor(self._t * 100.0)) #self._micros = micros # don't upgrade instances in place return micros New patch at http://launchpadlibrarian.net/9811478/DateTime.patch Laurence ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Changing DateTime to use pytz
Jim Fulton wrote at 2007-10-4 13:37 -0400: ... It might be nice if we could get the fix in the hands of people before a new Zope release, although that may not be practical. I was thinking of releasing a separate DateTime distribution, but don't know if there would be an easy way to install it in such a way that it was ahead of the existing DateTime in the path. Maybe, you can provide it as a (kind of hotfix) product (then you are sure, it will be imported) and use monkey patching to fix DateTime? -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Changing DateTime to use pytz
On 10/5/07, Laurence Rowe [EMAIL PROTECTED] wrote: All the tests still pass if I comment out the assignment: def _upgrade_old(self): Upgrades a previously pickled DateTime object. micros = long(math.floor(self._t * 100.0)) #self._micros = micros # don't upgrade instances in place return micros That seems like a reasonable solution. (Although maybe _upgrade_old isn't the best method name then, but that's details ;) ), -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] AW: [Zope3-dev] I'd lobe to merge the zope3-dev and zope-dev lists
Betreff: [Zope3-dev] I'd lobe to merge the zope3-dev and zope-dev lists Any objections? This would basically involve retiring the zope3-dev list and moving zope3 developers to the zope-dev list. -1 Not that I'm not interested in what's going on in Zope 2, but the two list let me easy separate this two different topics. And it will allow me to read the Zope2 mails in digest mode if I don't have time to read all. Another reason for not to switch is the mailinglist observation in the different web apps out there. They are very usefull. btw, a cool app, this is another reason to keep the trunk up and running. I guess they checkout our code and count the lines ;-). See: http://www.ohloh.net/projects/4495?p=Zope+3 e.g. Codebase 97,598 LOC Effort (est.) 25 Person Years Project Cost $1,348,258 Regards Roger Ineichen Jim -- Jim Fulton Zope Corporation ___ Zope3-dev mailing list [EMAIL PROTECTED] Unsub: http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] AW: [Zope3-dev] I'd lobe to merge the zope3-dev and zope-dev lists
--On 6. Oktober 2007 03:16:53 +0200 Roger Ineichen [EMAIL PROTECTED] wrote: Betreff: [Zope3-dev] I'd lobe to merge the zope3-dev and zope-dev lists Any objections? This would basically involve retiring the zope3-dev list and moving zope3 developers to the zope-dev list. -1 Not that I'm not interested in what's going on in Zope 2, but the two list let me easy separate this two different topics. And it will allow me to read the Zope2 mails in digest mode if I don't have time to read all. That's a bit shortsighted. First we want to get rid of the term Zope 3 in the future (since it confuses ppl). Second: decisions and discussons made in the Zope components world have an impact on the Zope 2 world. Sorry to say but the Zope components world is not an island. Andreas pgpzlndwCjQbg.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope] object Last Modified Date Time
Dear All, I want to store the object Last Modified in ZCatalog so i created a FieldIndex with name bobobase_modified_time. When i checked the Zcatalog the space for bobbase_modified_time is empty. Thx kamal.___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] object Last Modified Date Time
http://mail.zope.org/pipermail/zope/2002-October/124979.html - Original Message - From: kamal hamzat To: zope@zope.org Sent: Friday, October 05, 2007 5:31 PM Subject: [Zope] object Last Modified Date Time Dear All, I want to store the object Last Modified in ZCatalog so i created a FieldIndex with name bobobase_modified_time. When i checked the Zcatalog the space for bobbase_modified_time is empty. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] object Last Modified Date Time
--On 5. Oktober 2007 16:31:57 +0100 kamal hamzat [EMAIL PROTECTED] wrote: Dear All, I want to store the object Last Modified in ZCatalog so i created a FieldIndex with name bobobase_modified_time. When i checked the Zcatalog the space for bobbase_modified_time is empty. What means the space .. is empty? Standard Zope objects are *not* automatically indexed. Either you index them manually, programmtically or you check for CatalogAwareness (your magic search term). No idea what you're trying to build but you might choose CMF as a implementation form (dealing with indexing automatically). -aj pgpKHXD10KiKu.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] object Last Modified Date Time
kamal hamzat wrote at 2007-10-5 16:31 +0100: ... I want to store the object Last Modified in ZCatalog so i created a FieldIndex with name bobobase_modified_time. When i checked the Zcatalog the space for bobbase_modified_time is empty. It is *VERY* important that you are precise: both when you code as well as when you are posting questions: The method is bobobase_modification_time not bobobase_modified_time. -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
