[Zope-dev] Track modification
I want to track modifications of objects and I don't know when Zope changes the bobobase_modification_time. Is there a method I could overwrite for this? Thanks, Cornel ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] ClientCache and Large Files
Hello, We're running ZEO with Zope 2.5.1. We currently have a ZEO Cache (ClientCache) of 200 meg. Occasionally someone will download a 300 meg file that completely blows away the client cache. Is there a way to prevent this? Thanks, -Brian Brinegar ECN Purdue University ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] debugging Zope - ImportError: ./ExtensionClass.so: undefined symbol: PyObject_Init
Hi everybody,
I tried to follow Chapter 7: Testing and Debugging of The Zope Developer's
Guide (Zope 2.4 edition)
http://www.zope.org/Documentation/Books/ZDG/current/TestingAndDebugging.stx
However, on my Linux server I get the following error:
(Zope is v2.5.1)
[root@prefect Zope-2.5.1-linux2-x86-dev]# cd lib/python
[root@prefect python]# python
Python 1.5.2 (#1, Apr 3 2002, 18:16:26) [GCC 2.96 2731 (Red Hat Linux
7.2 2 on linux-i386
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
import Zope, ZPublisher
Traceback (innermost last):
File stdin, line 1, in ?
File Zope/__init__.py, line 21, in ?
import ZODB, ZODB.ZApplication, imp
File ZODB/__init__.py, line 14, in ?
import sys, ExtensionClass, TimeStamp, cPersistence, Persistence
ImportError: ./ExtensionClass.so: undefined symbol: PyObject_Init
The system is a RedHat 7.2 system with the following python packages
installed:
[root@prefect python]# rpm -qa | grep python
python-1.5.2-38
python-popt-0.8.8-7.x.2
python-xmlrpc-1.5.1-7.x.3
python2-docs-2.2-16
python2-2.2-16
python-clap-1.0.0-3
rpm-python-4.0.4-7x.18
python-docs-1.5.2-38
BTW, if I try to import ZPublisher only, the result is again an error:
[root@prefect python]# python
Python 1.5.2 (#1, Apr 3 2002, 18:16:26) [GCC 2.96 2731 (Red Hat Linux
7.2 2 on linux-i386
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
import ZPublisher
Traceback (innermost last):
File stdin, line 1, in ?
File ZPublisher/__init__.py, line 23, in ?
from Publish import publish_module, Retry
File ZPublisher/Publish.py, line 19, in ?
from Response import Response
File ZPublisher/Response.py, line 13, in ?
import HTTPResponse
File ZPublisher/HTTPResponse.py, line 79, in ?
status_codes[''.join(val.split(' ')).lower()]=key
AttributeError: 'string' object has no attribute 'join'
It seems I missed something important. Can anybody give me hint?
Yours. Jens
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ClientCache and Large Files
We're running ZEO with Zope 2.5.1. We currently have a ZEO Cache (ClientCache) of 200 meg. Occasionally someone will download a 300 meg file that completely blows away the client cache. Is there a way to prevent this? I'm afraid not; this isn't a very typical use case. You could implement a file size limit, or increase the cache size to be more than twice the largest expected dowload (the cache is implemented as two files, each of which is limited to half the nominal cache size). --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] debugging Zope - ImportError: ./ExtensionClass.so: undefined symbol: PyObject_Init
I tried to follow Chapter 7: Testing and Debugging of The Zope Developer's Guide (Zope 2.4 edition) http://www.zope.org/Documentation/Books/ZDG/current/TestingAndDebugging.stx However, on my Linux server I get the following error: (Zope is v2.5.1) [root@prefect Zope-2.5.1-linux2-x86-dev]# cd lib/python [root@prefect python]# python Python 1.5.2 (#1, Apr 3 2002, 18:16:26) [GCC 2.96 2731 (Red Hat Linux Um, Zope 2.5.1 requires Python 2.1.3 or later. You're using Python 1.5.2 here. That's probably the cause of the problems. --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ClientCache and Large Files
On Monday 16 December 2002 10:53 am, Guido van Rossum wrote: We're running ZEO with Zope 2.5.1. We currently have a ZEO Cache (ClientCache) of 200 meg. Occasionally someone will download a 300 meg file that completely blows away the client cache. Is there a way to prevent this? You're best bet would be to put a proxy cache in front of Zope. Zope's not very efficient at serving big static files like this compared to Apache or squid. I'm afraid not; this isn't a very typical use case. You could implement a file size limit, or increase the cache size to be more than twice the largest expected dowload (the cache is implemented as two files, each of which is limited to half the nominal cache size). I think it would be nice to be able to control cacheability of certain objects. However it smells like a YAGNI, especially with good front end caches that can take care of it. -Casey ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Infuriating ZClass registry Heisenbug
My trunk and 2.6 sandboxes are now behaving themselves. Thanks, guys! ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Infuriating ZClass registry Heisenbug
I'll have to take a look, but may not get to it today. FWIW I thought I fixed the bug on Friday. I could certainly create ZClasses through the web without getting any obvious errors. Jeremy ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Infuriating ZClass registry Heisenbug
On Monday 16 December 2002 11:55 am, Evan Simpson wrote: My trunk and 2.6 sandboxes are now behaving themselves. Thanks, guys! Ok, then it must be time for some more beautification... ;^) Idle hands are the work of the devil you know. -Casey ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Infuriating ZClass registry Heisenbug
Jeremy Hylton wrote: I'll have to take a look, but may not get to it today. FWIW I thought I fixed the bug on Friday. I could certainly create ZClasses through the web without getting any obvious errors. My little test (attached to the patch submission) passes with my version as well as your version, so it'll work. My patch was a lot simpler, though! :-) We need to add at least one unit test. testBug.py is a start. Do you want to convert it to a unit test or should I? If I do it, which of the myriad of ZODB branches should I add it to? :-) Shane ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Infuriating ZClass registry Heisenbug
The nice thing about fixing this bug is that the code continues to be improved. The last round of beautification made the code substantially more readable. This was a direct result of trying to track down a reference count problem. The problem proved to be elsewhere, but it was nearly impossible for me to inspect the old coptimizations.c code to figure out if the problem was there. If we make the code easier to read, we reduce the burden we all share more keeping the software working. Inscrutable code hides subtle bugs and encourages work arounds that make the whole system harder to understand. Jeremy ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] debugging Zope - ImportError: ./ExtensionClass.so: undefined symbol: PyObject_Init
Am Montag, 16. Dezember 2002 16:54 schrieb Guido van Rossum: I tried to follow Chapter 7: Testing and Debugging of The Zope Developer's Guide (Zope 2.4 edition) http://www.zope.org/Documentation/Books/ZDG/current/TestingAndDebugging.s tx However, on my Linux server I get the following error: (Zope is v2.5.1) [root@prefect Zope-2.5.1-linux2-x86-dev]# cd lib/python [root@prefect python]# python Python 1.5.2 (#1, Apr 3 2002, 18:16:26) [GCC 2.96 2731 (Red Hat Linux Um, Zope 2.5.1 requires Python 2.1.3 or later. You're using Python 1.5.2 here. That's probably the cause of the problems. Thank you for pointing this out. Just for the records: I tried Python 2.2, but this didn't work either. (This seems to be true for Zope-2.6.0, too) Then I installed Python 2.1.3 and this works. Great. However, there seems to be an easier solution: just use $ZOPE_HOME/bin/python ... Jens ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] realtime Bug Day report
So far the good folks participating in the bug day on irc.openprojects.net #zope-dev have resolved 13 issues in the collector. Present in the channel are 9 people. Feel free to join in. Thanks, - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] more bug day status
26 issues closed. Only 222 more to go. ;-) Notable bugs fixed: - multiple selection unicode bug (#697) - make sure passwords aren't encrypted twice ;-) (#256) - don't fail in History tab if Historical object is stored in a non-history-supporting storage (#700) 10 people currently in the #zope-dev channel on irc.openprojects.net. - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Infuriating ZClass registry Heisenbug
Yes, except I would argue that such work is best left on the HEAD rather than applied to a maintenance branch until necessitated by bug reports on that branch, or at least the knowledge that such a bug definitely exists and can be reproduced on that branch. I'm all for improving the code base. We just need to excercise caution changing code on maintenance branches unnecessarily. The HEAD is another matter, IMO go nuts! -Casey On Monday 16 December 2002 12:29 pm, Jeremy Hylton wrote: The nice thing about fixing this bug is that the code continues to be improved. The last round of beautification made the code substantially more readable. This was a direct result of trying to track down a reference count problem. The problem proved to be elsewhere, but it was nearly impossible for me to inspect the old coptimizations.c code to figure out if the problem was there. If we make the code easier to read, we reduce the burden we all share more keeping the software working. Inscrutable code hides subtle bugs and encourages work arounds that make the whole system harder to understand. Jeremy ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Infuriating ZClass registry Heisenbug
The nice thing about fixing this bug is that the code continues to be improved. The last round of beautification made the code substantially more readable. This was a direct result of trying to track down a reference count problem. The problem proved to be elsewhere, but it was nearly impossible for me to inspect the old coptimizations.c code to figure out if the problem was there. If we make the code easier to read, we reduce the burden we all share more keeping the software working. Inscrutable code hides subtle bugs and encourages work arounds that make the whole system harder to understand. +1. Remember the XP dogma: refactor mercilessly. --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Infuriating ZClass registry Heisenbug
CD == Casey Duncan [EMAIL PROTECTED] writes: CD Yes, except I would argue that such work is best left on the CD HEAD rather than applied to a maintenance branch until CD necessitated by bug reports on that branch, or at least the CD knowledge that such a bug definitely exists and can be CD reproduced on that branch. The work was all done on the trunk, but no one noticed before Zope 2.6 was released. Jeremy ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Track modification
On Mon, 16 Dec 2002, Cornel Nitu wrote: I want to track modifications of objects and I don't know when Zope changes the bobobase_modification_time. Is there a method I could overwrite for this? No. Bobobase_modification_time is the timestamp in the ZODB (the database) when the object record was last modified. If you want to track modification times that have some other definition, you'll have to create your own tracking infrastructure (a property on your objects and appropriate code to update it). --RDM ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] ClientCache and Large Files
This sounds like the most appropriate solution, as long as you are careful to make sure that Squid or other forward cache is configured to cache files that large, it isn't likely going to be by default. Sean -Original Message- From: Casey Duncan [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 8:21 AM To: Guido van Rossum; Brian R Brinegar Cc: [EMAIL PROTECTED] Subject: Re: [Zope-dev] ClientCache and Large Files On Monday 16 December 2002 10:53 am, Guido van Rossum wrote: We're running ZEO with Zope 2.5.1. We currently have a ZEO Cache (ClientCache) of 200 meg. Occasionally someone will download a 300 meg file that completely blows away the client cache. Is there a way to prevent this? You're best bet would be to put a proxy cache in front of Zope. Zope's not very efficient at serving big static files like this compared to Apache or squid. I'm afraid not; this isn't a very typical use case. You could implement a file size limit, or increase the cache size to be more than twice the largest expected dowload (the cache is implemented as two files, each of which is limited to half the nominal cache size). I think it would be nice to be able to control cacheability of certain objects. However it smells like a YAGNI, especially with good front end caches that can take care of it. -Casey ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.6.0 ZMI Problem for CJK(Collector 623) patch.
On Fri, 13 Dec 2002 11:12:22 +0900
Kazuya FUKAMACHI [EMAIL PROTECTED] wrote:
But, if it takes a few months or longer,
I will try to modify Russian patch as an experiment,
maybe taking in your approach in some degree.
Is that bad idea?
I believe it's good idea, as Russian patch's approach is a solid,
straightforward and standard way of I18N. Although not
good for M17N, the behaviour is simple straight so that it's
much less confusing for end-users (IMHO).
Probably os.environ.get('Z_SOMETHING') might be a better way than
locale.getlocale()[1], because using locale.getlocale()[1] means that
the behaviour of Zope will be changed implicitly, whereas
os.environ.get('Z_SOMETHING') is more explicit for the users, thus
less confusing..
Regards,
---
Heiichiro NAKAMURA [EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.6.0 ZMI Problem for CJK(Collector 623) patch.
Hi.
Probably os.environ.get('Z_SOMETHING') might be a better way than
locale.getlocale()[1], because using locale.getlocale()[1] means that
the behaviour of Zope will be changed implicitly, whereas
os.environ.get('Z_SOMETHING') is more explicit for the users, thus
less confusing..
Nice idea.
We can get environment value everywhere in Zope.
it will be easy to make patch:-)
+1
Regards
--
Yusei
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [ZDP] Suggested documentation update.
Sounds good. Maybe we can just incorporate it into the Zope Book and ship the Book with Zope. On Mon, 2002-12-16 at 15:12, Lennart Regebro wrote: doc/WEBSERVERS.txt only mentiones CGI. I'd suggest that we rename it to CGI.txt and create a new APACHE.txt that takes up how to use Zope with Apache, and make a new WEBSERVERS.txt that refers to these two documents, with some description of when each should be used. I can make the APACHE.txt building on my Apache how-to. Thoughts? ___ ZDP maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zdp ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.6.0 ZMI Problem for CJK(Collector 623) patch.
On Tue, 17 Dec 2002 11:08:19 +0900
Yusei Tahara [EMAIL PROTECTED] wrote:
NAKAMURA wrote:
Probably os.environ.get('Z_SOMETHING') might be a better way than
locale.getlocale()[1], because using locale.getlocale()[1] means that
the behaviour of Zope will be changed implicitly, whereas
os.environ.get('Z_SOMETHING') is more explicit for the users, thus
less confusing..
Nice idea.
We can get environment value everywhere in Zope.
it will be easy to make patch:-)
+1
Zope 2.6.x has LOCALE_ID in 'z2.py' to set locale value.
If LOCALE_ID is set to something, locale.getlocale()[1] is sure
to get this value, because locale.setlocale(locale.LC_ALL, val)
is called from 'z2.py'.
For this reason, if you set LOCALE_ID, locale.getlocale()[1] does not
mean that behaviour of Zope will be changed implicitly, but rather
explicitly, I think.
I'm not sure which is better;
1) adopting new environment value, Z_SOMETHING
ie. Z_DEFUALT_CHARSET ?
2) using locale.getlocal()[1]
needs some abstruction layer
def getDefaultPythonCharEncodingName():
if os.name == 'posix':
return charEncodingMap.get(locale.getlocale()[1], 'latin1')
else: # For MS Windows
return os.environ.get('Z_CHAR_ENCODING', 'latin1')
[snip]
Any comments are welcomed.
Regards,
Kazuya Fukamachi
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [ZDP] Suggested documentation update.
I'd like to make a (blatantly self serving :-) sugestion: Andy has passed the mantainership of the ASP404 script to us http://www.zope.org/Members/hiperlogica/ASP404 As far as I can tell, it's the best (least worse? :-) solution to connect IIS to Zope as it is the easiest to setup (and get right) and has an acceptable performance (as compared to pcgi.exe, which is dog slow and difficult to setup, and fastcgi, which I could never get to work with IIS). Since we intend to mantain it until a better solution emerges, I'd appreciate if it could be mentioned in the official docs. I'd be willing to write the text that goes into WEBSERVERS.txt (or it's offspring, say, ASP404.txt). On Mon, 2002-12-16 at 01:11, Chris McDonough wrote: Sounds good. Maybe we can just incorporate it into the Zope Book and ship the Book with Zope. On Mon, 2002-12-16 at 15:12, Lennart Regebro wrote: doc/WEBSERVERS.txt only mentiones CGI. I'd suggest that we rename it to CGI.txt and create a new APACHE.txt that takes up how to use Zope with Apache, and make a new WEBSERVERS.txt that refers to these two documents, with some description of when each should be used. I can make the APACHE.txt building on my Apache how-to. Thoughts? ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
