I have two versions of Zope running... My clients version, which is Linux and an original Zope 1.10.3 ... (Awww... old, I know)... My local version, which is Win32 and Zope 1.10.3 ... (Old version, new installation, aye...) Now, after fighting an uneven battle against a Win32 installation of MySQL-Python/MySQLDA etc. for some time, I finally succeeded to import the application to my workstation. And incredibly enough, most of it worked, which I thoguht was too good to be true... eh ... Now, yes - really. It was too good to be true, because parts of the application pages proved to fail due to a couple of minor lines in the code... Now, it seems to be the following lines, related to ZopeTime and which format to use... (This actually works on the Zope 1.10 linux installation, but not on my Win32 installation)... <!--#call "REQUEST.set('todate', ZopeTime()+1)"--> And another line... <!--#call "REQUEST.set('fromdate', ZopeTime('%s/%s/%s' % (from_year, from_month, from_day)))"--> Now, being the true Zope (python) newbie as I am, I admit this looks pretty cool. And logic. But the logic stops working right about why it works on one Zope 1.10.3 installation but not on the other. Is this ZopeTime() thing calling a function in Python? Is it a chance that my Python installation (Zope 1.10.3 comes with Python 1.5 eh?) is not the same as the one on the Linux box? ... Now, I think I have installed Python 2.2 on this workstation. (Any way I can check which Python version Zope calls except decoding those cryptic "innermost traceback" -messages? Any ideas? Workarounds? Also... would any of you guys happen to have documentation to Zope 1.10, eventually where I can find it? What I have is pretty limited, and my client doesnt really understand the words "hard to do", "obsolete" and "no documentation" ... he keeps repeating "you fix, you smart, you computer guy, right?" all the time ... Best regards, Robert.
On Wed, Nov 12, 2003 at 02:02:24PM -0200, Robert Restad wrote:
Is this ZopeTime() thing calling a function in Python?
everything in zope calls functions in python sooner or later.
Is it a chance that my Python installation (Zope 1.10.3 comes with Python 1.5 eh?) is not the same as the one on the Linux box?
That's possible. Zope is usually rather particular about what versions of python are supported. The windows install should use the bundled version, but it's worth checking.
... Now, I think I have installed Python 2.2 on this workstation. (Any way I can check which Python version Zope calls except decoding those cryptic "innermost traceback" -messages?
They're not cryptic but very very useful once you get used to them :-) And yes, you can check the management interface -> Control Panel. It should tell you the version of python in use. (Assuming this feature existing in zope 1, I can't vouch for that.) It might also be printed during the start-up messages. -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's THE VOLUPTOUS HAIR! (random hero from isometric.spaceninja.com)
Hey Paul... Here is the Zope CP info I have... Linux Box: You are running Zope version: Zope 1.10.3 (source release, python 1.5.1, linux2), on Python 1.5.2 (#0, Dec 27 2000, 13:59:38) [GCC 2.95.2 20000220 (Debian GNU/Linux)] on linux2 Win32: You are running Zope version: Zope 1.10.3 (binary release, python 1.5.1, win32-x86), on Python 1.5.1 (#0, Nov 18 1998, 12:17:58) [MSC 32 bit (Intel)] on win32. Now, would it be possible that this minor difference actually justifies the DateTime() problem? (Python 1.5.2 vs. 1.5.1) Best regards Robert. ----- Original Message ----- From: "Paul Winkler" <pw_lists@slinkp.com> To: <zope@zope.org> Sent: Wednesday, November 12, 2003 2:33 PM Subject: Re: [Zope] ZopeTime() trouble.
On Wed, Nov 12, 2003 at 02:02:24PM -0200, Robert Restad wrote:
Is this ZopeTime() thing calling a function in Python?
everything in zope calls functions in python sooner or later.
Is it a chance that my Python installation (Zope 1.10.3 comes with Python 1.5 eh?) is not the same as the one on the Linux box?
That's possible. Zope is usually rather particular about what versions of python are supported. The windows install should use the bundled version, but it's worth checking.
... Now, I think I have installed Python 2.2 on this workstation. (Any way I can check which Python version Zope calls except decoding those cryptic "innermost traceback" -messages?
They're not cryptic but very very useful once you get used to them :-) And yes, you can check the management interface -> Control Panel. It should tell you the version of python in use. (Assuming this feature existing in zope 1, I can't vouch for that.) It might also be printed during the start-up messages.
--
Paul Winkler http://www.slinkp.com Look! Up in the sky! It's THE VOLUPTOUS HAIR! (random hero from isometric.spaceninja.com)
_______________________________________________ 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 )
On Wed, Nov 12, 2003 at 04:11:18PM -0200, Robert Restad wrote:
Hey Paul...
Here is the Zope CP info I have...
Linux Box: You are running Zope version: Zope 1.10.3 (source release, python 1.5.1, linux2), on Python 1.5.2 (#0, Dec 27 2000, 13:59:38) [GCC 2.95.2 20000220 (Debian GNU/Linux)] on linux2
Win32: You are running Zope version: Zope 1.10.3 (binary release, python 1.5.1, win32-x86), on Python 1.5.1 (#0, Nov 18 1998, 12:17:58) [MSC 32 bit (Intel)] on win32.
Now, would it be possible that this minor difference actually justifies the DateTime() problem? (Python 1.5.2 vs. 1.5.1)
Sorry, I've no idea specifically. If I were you I'd just try it. -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's GIRL-WENCH! (random hero from isometric.spaceninja.com)
Here is the Zope CP info I have...
Linux Box: You are running Zope version: Zope 1.10.3 (source release, python 1.5.1, linux2), on Python 1.5.2 (#0, Dec 27 2000, 13:59:38) [GCC 2.95.2 20000220 (Debian GNU/Linux)] on linux2
Win32: You are running Zope version: Zope 1.10.3 (binary release, python 1.5.1, win32-x86), on Python 1.5.1 (#0, Nov 18 1998, 12:17:58) [MSC 32 bit (Intel)] on win32.
Now, would it be possible that this minor difference actually justifies the DateTime() problem? (Python 1.5.2 vs. 1.5.1)
It's extremely possible. There's a reason 1.5.2 is still The Python Version and 1.5.1 isn't. You should try and see if that's the problem. The other issue is that Python has different time implementations between Unix and Windows, since it relies on the OS's c libraries. I think I remember that there's no strptime (string parse time) function in the Windows C library. I think this is still true, in fact, though there are pure-Python implementations now. http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/56036 I think that current versions of Zope's DateTime use one of these to get around this problem, but who knows about the version you have. One other problem may be Y2K. The Python time module was fixed in 1.5.2 for Y2K problems. --jcc -- "My point and period will be throughly wrought, Or well or ill, as this day's battle's fought."
participants (3)
-
J. Cameron Cooper -
Paul Winkler -
Robert Restad