Re: [Zope] Weird undefined symbol: PyUnicodeUCS{2|4}_AsEncodedString errors
You probably have two different versions of Python installed. And probably this is a 64-bit system at least in parts. Check the python path cron uses and compare to the path the instance is run with. HTH, __Janko Am 18.02.2009 um 11:37 schrieb Chris Withers: Hi All, I wonder if anyone has seen errors like these before... Scenario is as follows, two Zope instances and a zeo server all running from the debian zope2.9 packages. All the control scripts for these instances fail with the following error when used: Traceback (most recent call last): File /usr/lib/zope2.9/lib/python/Zope2/Startup/zopectl.py, line 322, in ? main() ... File /usr/lib/zope2.9/lib/python/persistent/__init__.py, line 19, in ? from cPersistence import Persistent, GHOST, UPTODATE, CHANGED, STICKY ImportError: /usr/lib/zope2.9/lib/python/persistent/cPersistence.so: undefined symbol: PyUnicodeUCS4_AsEncodedString However, when run as a cron job as follows: @daily /var/lib/zope2.9/instance/x/bin/zopectl run /var/lib/zope2.9/instance/x/Products/Stepper/run.py -q / jobs ...the control scripts behave properly and the stepper jobs get run. To solve the problem, I built python from source and installed the latest Zope 2.9 from source. Now, all the instances behave fine, except the above cron job now fails with the following: Traceback (most recent call last): File /opt/Zope-2.9/lib/python/Zope2/Startup/zopectl.py, line 334, in ? exitstatus = main() ... File /opt/Zope-2.9/lib/python/persistent/__init__.py, line 19, in ? from cPersistence import Persistent, GHOST, UPTODATE, CHANGED, STICKY ImportError: /opt/Zope-2.9/lib/python/persistent/cPersistence.so: undefined symbol: PyUnicodeUCS2_AsEncodedString So, the problem seems inverted now and the error is about UCS2 rather than UCS4. Anyone ever seen anything like this? What is that symbol and why would it be there when run from a shell and not there when run from cron? cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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 ) PGP.sig Description: Signierter Teil der Nachricht ___ 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] pickle passing over a socket
Am 22.08.2008 um 19:43 schrieb David Bear: On 8/22/08, Andrew Milton [EMAIL PROTECTED] wrote: +--- [ David Bear ]-- | It seems to me that it could be usefull to have a zope method for passing | python pickles to external processes through a unix domain socket. My thinking | was to use this as a means to abstract a data base connection. Yes, I know | there are zsql methods, sqlalchemy and other products to do this. But my | thought was to have a generilzed method for just passing a pickle to an | external process that could do anything with it. Perhaps it could pass a pickle | to a queue that would handle the pickle if the site need some high volume | handling of data. | | Then one could have another python process listening on the socket -- ready to | receive pickles for zope. Isn't this called ZEO? d8) ZEO could be a model for this - but ZEO stores the pickles to zodb. What if I wanted to queue the pickle up and take some kind of long term processing action on it? Store it in a network file system -- which may have a high write latency to, put it in a data base for which there were no zope connectors, etc. Queuing, async long term processing, eventsystem are very different requirements. They have only a small part on the protcoll level, the more complex part is the logic at the recieving end. And it is easier, to call remote procedures or methods with local data, than to push pickles down a socket and decide what to do with them. There are a number of packages wich do that and much more at a higher level. I would look at http://pyro.sourceforge.net/ http://foolscap.lothar.com/trac http://threekong.com/ On the protcoll level, there are many modern contributions from the bigheads at google and facebook, like Protobufs, thrift, amqp (http://barryp.org/software/py-amqplib/ ) HTH, __Janko PGP.sig Description: This is a digitally signed message part ___ 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] Counting the elements of a result in a ZCatalog
Am 05.06.2008 um 12:56 schrieb Marco Bizzarri: Hi all. I need to query a ZCatalog, and I would like to know how many elements are there. I'm working from inside a python product, so, I could do something like: results = Catalog(criteria) return len(results) But this creates a number of objects which are completly useless for me. After all, I'm interested in just the length, not in the objects. I could do something like this: results = Catalog(criteria, sort_limit=1) return results.actual_result_count since I should have a LazyMap, which does not (should not) actually load all the objects (at least, I hope so). This does not work if I have no result. So, what I should do would be: results = Catalog(criteria, sort_limit=1) if len(results) == 0: return 0 return results.actual_result_count Am I missing something? Yes, you do the expensive operation just for the test, so there is no benefit. if result: result_len = results.actual_result_count else: result_len = 0 return result_len HTH, __Janko PGP.sig Description: This is a digitally signed message part ___ 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] [buildout] bootstrap and develop
Am 06.02.2008 um 19:07 schrieb Tarek Ziadé: Maurits van Rees-3 wrote: ... 2. What would be alternatives or how can this be changed? You can use the z3c.recipe.egg:editable recipe. I briefly tried that, but it did not work for our (Zest Software) internal password protected subversion repository, where we keep the code for our clients. The recipe tries to easy_install a package but it fails as it cannot use our repository without a password. You can use the #egg trick within the [buildout] find-links variable, then add lovely.buildouthttp to take care of the svn login. Thanks for yours and Maurits hints. I actually tried the recipe Maurits mentioned without success, but just yesterday an extension was published at pypi, which does exactly solves this problem. http://pypi.python.org/pypi/gp.svndevelop/0.1 Besides I didn't know that there is an extension mechanism besides recipes. One of our repositories is also password protected, but after the first successful login with an interactive svn session on the console this is not an actual issue. With regards and appreciation for the help __Janko Hauser ___ 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 )
[Zope] [buildout] bootstrap and develop
Hello, I'm using the infrae.subversion recipe to collect various Products and packages from our subversion. The main goal here is, to not use svn:externals. But the buildout directive develop=src/... seems to have the requirement, that the packages are already present if bootstrap.py is called. So it is not possible to place packages there with buildout and get them picked up. 1. Is this correct? I searched and found others have the same problem. 2. What would be alternatives or how can this be changed? Thanks for answers and hints, __Janko Hauser ___ 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-dev] Request typing (to get the xmlrpc layer discussion finished)
Am 17.12.2007 um 15:40 schrieb Jim Fulton: On Dec 17, 2007, at 8:22 AM, Christian Zagrodnick wrote: Hi, a couple of weeks ago there was some discussion about the skin/ layer support for XML-RPC which I implemented without asking (shame on me). As some time has passed now everybody could have some fresh thoughts about it. Let me first summarise: * Skin and layers should be seen as typing the request. * There are no general objections against having layers for XML-RPC. I have a general objection for reasons of complexity. Why do we need this? About the specifics with skins for other protocols than http I can not say much. In fact, I find skins in general to introduce more complexity than they're worth. This baffles me somewhat. At the moment I see skins/layers as the only mechanism to let developers using an application to customize it, possibly more than once in the same instance. I find them not optimal, because they only allow customizing on the outer most level. But overrides is a failure as I understand it. I understand, that there is a trend to distinguish between libraries (with less zcml) and applications (with zcml to configure reused libraries). But on the level of applications I know of no other mechanism than layers. So what should be used or invented instead? As a usecase take a forum application which should be installed more than once in an instance but needs different layouts and also different subset of functionality. With regards, __Janko -- Janko Hauser email: [EMAIL PROTECTED] mobile: +49 1721 641552 PGP.sig Description: Signierter Teil der Nachricht ___ 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] Request typing (to get the xmlrpc layer discussion finished)
Am 17.12.2007 um 16:16 schrieb Jim Fulton: On Dec 17, 2007, at 10:07 AM, Janko Hauser wrote: ... This baffles me somewhat. At the moment I see skins/layers as the only mechanism to let developers using an application to customize it, possibly more than once in the same instance. I find them not optimal, because they only allow customizing on the outer most level. But overrides is a failure as I understand it. How are overrides a failure? Perhaps I do not understand them good enough, but application developers can not use them, as there can be different applications by other developers overriding the same. Integrators could use them to overwrite everything, but only once. Skins, after all do nothing but override views. Yes, but by defining a scope, which can be made location aware, during traversal. ... So what should be used or invented instead? I use overrides. As a usecase take a forum application which should be installed more than once in an instance but needs different layouts and also different subset of functionality. I don't have this use case. I wonder how many people do. I think every multisite setup has this problem. We tend to think up complex use cases and then make the zope framework more complicated to deal with them. Sometimes these are legitimate use cases, but they are rarely common cases and their solutions should generally not be inflicted on the masses. WRT this use case, I strongly suspect it would be simpler and easier to support defining multiple configurations in ZCML and a mechanism to specify different configurations for different sites within an instance. In fact, I think Stephan Richter added this a while ago. Oh that would be a new information for me, so I would be very interested, where this is implemented. Thanks in advance __Janko -- Janko Hauser email: [EMAIL PROTECTED] mobile: +49 1721 641552 ___ 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] Request typing (to get the xmlrpc layer discussion finished)
Am 17.12.2007 um 16:34 schrieb Fred Drake: On Dec 17, 2007 10:32 AM, Janko Hauser [EMAIL PROTECTED] wrote: Oh that would be a new information for me, so I would be very interested, where this is implemented. z3c.baseregistry Uhu, thanks, this looks like it will open up many possibilities. And I'm sorry to have highjacked the original question. So back to Christians original question. With regards, __Janko -- Janko Hauser email: [EMAIL PROTECTED] mobile: +49 1721 641552 PGP.sig Description: Signierter Teil der Nachricht ___ 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] How to publish Zope2 products on PyPI
Am 22.09.2007 um 07:59 schrieb Dieter Maurer: My current ideas towards a solution: We define a package prefix for Zope2 products, e.g. zope2.products. Zope2 products are published to PyPI as prefix.productname. Searching for Products at PyPi results in a longer list. So I think a namespace is already present. We extend the Zope2 configuration with an option additional- products which lists the products used by the instance that are not at a standard place -- such as those installed by setuptools There is a directive in zope.conf to add additional directories to the products namespace. To add downloaded eggs to an instance one can set them in the PYTHONPATH environment variable. Buildout does it in the ./bin/ ctrlsrcipts These are only hints, because I also have severe difficulties to put all these things together. One point I do not understand is, how to build eggs from src checkouts in one buildout for zope2 without downloading all dependencies as eggs (which are also part of the main zope install) Is there actually a list, where buildout questions can be asked? With regards, __Janko -- Janko Hauser email: [EMAIL PROTECTED] mobile: +49 1721 641552 PGP.sig Description: Signierter Teil der Nachricht ___ 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: Interest in AdvancedQuery and/or ManagableIndex?
First let me say, that I'm in favour to add these products to Zope in some form, to take the chance to enhance the zcatalog significantly. Am 03.02.2007 um 14:34 schrieb Martin Aspeli: yuppie wrote: - Should we add new products to the core? I thought we want to move away from products and use python packages instead. The AdvancedQuery code might become part of the ZCatalog package, ManagableIndex might be converted to a non-products package. There are hardly new, though, they've been around for ages and have enthusiastic users. Those users always found it hard to convince people to adopt them more widely because they were not in the standard repositories and a bit scary That's clearly a point to make clear, that splitting the code or to do big refactorings needs someone with deep knowledge of the code and its dependancy into the cataloging framework. - I think any chance to resolve that should be taken. I'm quite bad for reshuffling code just for the sake of aesthetics, but I don't think having them as products should be any kind of barrier until products are officially deprecated (no, I didn't say that, let's not go there this decade). +1 I think the first step is svn.zope.org. That makes them accessible for other people to work on. Shipping with Zope 2.x may or may not be a worthwhile goal in the short term - probably we need someone to cut a branch, see what it would look like and collectively review that. Another point is that for example hurry is already using parts of the code. So there are possibilities to look for integration in zope3 too. With regards, __Janko -- Janko Hauser email: [EMAIL PROTECTED] mobile: +49 1721 641552 PGP.sig Description: Signierter Teil der Nachricht ___ 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: Interest in AdvancedQuery and/or ManagableIndex?
Replying to my own post, Am 03.02.2007 um 15:14 schrieb Janko Hauser: There are hardly new, though, they've been around for ages and have enthusiastic users. Those users always found it hard to convince people to adopt them more widely because they were not in the standard repositories and a bit scary That's clearly a point to make clear, that splitting the code or to do big refactorings needs someone with deep knowledge of the code and its dependancy into the cataloging framework. What I wanted to express here is, that the inclusion as products is somewhat easier and more clearly defined, than to do a complete integration and restructuring of the whole index framework/code. So I propose to do this in two or more steps. With regards, __Janko PGP.sig Description: Signierter Teil der Nachricht ___ 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-PAS] Domainauth
Am 22.06.2006 um 13:48 schrieb Zachery Bir: Woops. Like I said, too long since I played in it. It runs request.getClientAddr(), which does take HTTP_X_FORWARDED_FOR, but only if the default REMOTE_ADDR is in an attribute called `trusted_proxies`. From lib/python/ZPublisher/HTTPRequest.py (in some 2.7 branch): # The trusted_proxies configuration setting contains a sequence # of front-end proxies that are trusted to supply an accurate # X_FORWARDED_FOR header. If REMOTE_ADDR is one of the values in this list # and it has set an X_FORWARDED_FOR header, ZPublisher copies REMOTE_ADDR # into X_FORWARDED_BY, and the last element of the X_FORWARDED_FOR list # into REMOTE_ADDR. X_FORWARDED_FOR is left unchanged. # The ZConfig machinery may sets this attribute on initialization # if any trusted-proxies are defined in the configuration file. trusted_proxies = [] (again, this is all if you're using mod_rewrite and VirtualHostMonster) Thank you Zac, yes I'm using mod_rewrite and VHM. I added the trusty- proxy directive into etc/zope.conf, but this seems to not work. But on further on this route I added a patch from Dieter Maurer to SiteAccess/VHM and I have now the right REMOTE_ADDR in the request. But no access to secured pages :-) Another thing I noticed it, that I see that a user authenticated by the cookie-login runs through the code of domain_auth. And the cookie- plugin is used for credential extraction. As far as I understand, the actual authentication is done later. So if the cookie-plugin does not found an appropriate cookie it redirects to the login-page and the domain_auth plugin is never used? With regards and thanks for the help, __Janko -- Janko Hauser email: [EMAIL PROTECTED] mobile: +49 1721 641552 PGP.sig Description: Signierter Teil der Nachricht ___ Zope-PAS mailing list Zope-PAS@zope.org http://mail.zope.org/mailman/listinfo/zope-pas
Re: [Zope-PAS] Re: Domainauth
Am 22.06.2006 um 15:39 schrieb Tres Seaver:
The sequence which creates a user object is defined in the
PAS.validate
method:
...
Very good documentation snipped
I followed this path and found the culprit.
The cookie_auth_helper extends the credentials with the remote_addr
only if it found something before.
else:
# Look in the request for the names coming from the
login form
login = request.get('__ac_name', '')
password = request.get('__ac_password', '')
if login:
creds['login'] = login
creds['password'] = password
if creds or 1: # or 1 added by jhauser
creds['remote_host'] = request.get('REMOTE_HOST', '')
try:
creds['remote_address'] = request.getClientAddr()
except AttributeError:
creds['remote_address'] = request.get('REMOTE_ADDR',
'')
return creds
So actually the question is, if the test for credentials is needed at
all at this place.
I will further look into this, but thanks to Tres and ZAC to lead me
to this place.
With regards,
__Janko
--
Janko Hauser email: [EMAIL PROTECTED]
mobile: +49 1721 641552
PGP.sig
Description: Signierter Teil der Nachricht
___
Zope-PAS mailing list
Zope-PAS@zope.org
http://mail.zope.org/mailman/listinfo/zope-pas
Re: [Zope] [ANN] Zope 2.8.6 released
Am 10.03.2006 um 13:06 schrieb Luca Olivetti: En/na Andreas Jung ha escrit: Hi all, on behalf of Zope Corporation and the Zope community I am pleased to announce the release of Zope 2.8.6. You can download Zope 2.8.6 from http://www.zope.org/Products/Zope/2.8.6/ It's just me or the permissions are wrong? No I had the same expirience under MacOSX and debian system. __Janko Hauser ___ 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-PAS] Re: Moving PAS and PluginRegistry to SVN?
Am 09.10.2005 um 23:11 schrieb Jens Vagelpohl: On 9 Oct 2005, at 19:46, Rocky Burt wrote: What is the timeframe on this being done? Just so I know when to update my development versions of PAS. - Rocky Jens Vagelpohl wrote: I would volunteer to move both the PluggableAuthService and PluginRegistry products to svn.zope.org. Anyone have any thoughts about that? There is no time frame. Only Zac has responded and I'm not sure if that constitutes enough assent. Oh, I thought that silence is counted as not against it :-). I for one would be in favour of this move, and also about further ideas to incorporate it into one of the coming Z2 releases. with regards, __Janko ___ Zope-PAS mailing list Zope-PAS@zope.org http://mail.zope.org/mailman/listinfo/zope-pas
Re: [Zope-dev] Zope 2.9 goals
Am 17.06.2005 um 11:45 schrieb Martijn Faassen: Hi there, Since Zope 2.8 has now been released, we can start talking about what would be in Zope 2.9. I have some ideas: * newer version of Five included (whatever version is current then) * Zope 3.1 included * Python 2.4 support +1 although 2.4 support is mainly a policy and auditing process, as some are apparently already running zope on python 2.4. How is this auditing performed? I think these could all be accomplished without getting too ambitious. Especially the Five work and Zope 3.1 work will mostly happen anyway, so integration should be relatively easy. I don't know much about how involved Python 2.4 support would be; perhaps people who know more can speak up. Then there's something I know little about, but is also believed planned for Zope 2.9: * blob storage, file iterators If I'm not mistaken, file iterators are already part of Zope2.8 or do you mean the interaction between blob storage and file iterators? Looking forward to it, __Janko ___ 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-PAS] Re: Test fixes for pre-1.1 release
Am 17.06.2005 um 17:55 schrieb Zachery Bir: I'm working on the head with some unchecked-in changes. The current head incorporates the initial work in demangling ids. Thanks for the info. __Janko ___ Zope-PAS mailing list Zope-PAS@zope.org http://mail.zope.org/mailman/listinfo/zope-pas
Re: [Zope] Max Connections
Am 03.06.2005 um 12:54 schrieb Germer, Carsten: Pascal, Would you be so kind to send the zodb-part of your config? I Increased the zserver-threads for exactly the mentioned reasons but I was not aware of the connectio pool-parameter, nor can I find it anywhere in my zope.conf :) Carsten look into lib/python/ZODB/component.xml There are all ZConfig directives defined and their defaults. From this I would assume the following ZODB config zodb_db main # Main FileStorage database filestorage path $INSTANCE/var/Data.fs /filestorage mount-point / cache-size 8000 pool-size 15 /zodb_db HTH, __Janko ___ 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: [Zope3-dev] Re: [Zope-dev] Re: Five and 2.9
Martijn Faassen wrote: There's the 'approach' and the implementation. The approach is fairly clear: a focus on baby steps to integrate into Zope 2.7. The aim is to introduce as much as possible as make sense of Zope 3 facilities into Zope 2. Besides ourself also Christian Heimes has done a more product oriented adoption of the adapter and interfaces stuff. Will it be possible to use five in this way? The implementation is still flux. Though that said, things like interfaces and adapters should be stable enough (as long as Zope 3 is stable in that regard), as there's really no difference between the way Five does them and the way Zope 3 does them. For views, we're moving along nicely following the Zope 3 pattern. At the post-Europython sprint Stuart Bishop and I, with help from Jim, came up with a way to integrate them the right way for Zope 2 objects. I'm now pretty happy with them, though some more possibilities and details are bound to change still. You can now even add views to existing Zope 2 objects, without the /edit/ hack, from ZCML. That this happens by way of Structured Monkeypatching shouldn't concern anybody. ;) Will this monkeypatch be somewhat of a blessed way to include view adapters into zope2? Than we can replace our current approach of using view adapters in union.cms with this one. Or will this be integrated into Zope 2.8 at the end? While Five is in flux, I expect the main changes you'll have to make in your applications is slightly altering some ZCML statements and possibly changing an import here and there. It also depends on who contributes what, as always. :) On the conference you suggested to setup a mailinglist for the discussion of interface integration. Sure the main parts are done, but I think it would also be nice to see, how different projects are actually using the new possibilities. For example the usage of widgets can lead to something like a layout-manager or some other tools to really integrate them into Zope 2 applications. I think it would also drive some more testing and zope3 and further integration of other parts. (If one has views, adapters, schemas and widgets, events are looming in the corner :-) With regards, __Janko Hauser ___ Zope-Dev maillist - [EMAIL PROTECTED] 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: Caching prob with AHCM and headers
On Thu, 11 Sep 2003 09:59:22 +0800 Bjorn Stabell [EMAIL PROTECTED] wrote: Setting Last-Modified to the current time isn't always the right thing; some objects, .e.g., Files, Images, Documents, have last modification times, and using those would be better. Not sure if the accelerator can be smart enough to know about these, though. I think, this is one problem with the current code. There is no defined way to decide, when something is last modified. With CMF-based sites there is a clearly defined property for this. On the other hand all objects have at least a bobobase_modification_time, but this one changes with every ZODB action on the object. I'm not sure what to do. __Janko ___ Zope-Dev maillist - [EMAIL PROTECTED] 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] DateTime.rfc822() bug?
Lennart Regebro wrote: From: Geir Bækholt [EMAIL PROTECTED] i can confirm that this is a bug in DateTime.rfc822(), and that rfc-conformant mailclients choke on it aswell.. Oh, man, I've looked at DateTime now, and it's a mess... (ar at least, the timeone hadnling is). I'm seriously considering making rfc822() into this: def rfc822(self): Return the date in RFC 822 format return '%s, %2.2d %s %d %2.2d:%2.2d:%2.2d %s' % ( self._aday,self._day,self._amon,self._year, self._hour,self._minute,self._nearsec,'-') That would return the RFC2822 format that explicitly specifies that there is no timezone information included... At least that would make it compliant. :-/ A better way would be storing the timzone offset internally in the DateTime object and using it, but there timezone handling is spread out all over the place, so I haven't really gotten a grip on it yet. Zope3 already uses the experimental datetime from Python2.3. From a quick look it seems to handle timezones. Perhaps you can look there for some ideas or use it instead. HTH, __Janko ___ 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] Speaking of 2.6...
On Tue, 9 Apr 2002 13:47:49 -0400 Brian Lloyd [EMAIL PROTECTED] wrote: ...I sent out a note a while ago now trying to scare up some ideas on how to vet the current list of 2.6 proposals and get to a final plan. I didn't get much (any?) response :( Hello Brian, just to give some feedback and ask for guidance with the further process. My college, Nils Kassube, has implemented the proposed features, regarding an enhanced MailHost, namely the usage of timeoutsocket in the SMTP-module and the archiving of outgoing mails. We also asked the programmer of timeoutsocket for permission, although the module has a BSD-license. He has no problem with the incorporation of the module into the Zope2 code base. Our current plan is to upload a patch to the collector, so other people, specifically people with a server setup under windows can test this and to send a note to Zope-Dev seeking for feedback. I have checkin privileges and also signed the the necessary papers, so later I can integrate the patch into the code base. Would it be enough to put a documentation in the proposal wiki and is the proposal sufficient? Should we take other actions? We would like to have this incorporated. Please take this mail as a commitment notification :-). Thanks for any answers, with regards, __Janko Hauser -- i.A. Dr. Janko Hauser Software Engineering c o m . u n i t G m b H online-schmiede seit 1994 http://www.comunit.de/ mailto:[EMAIL PROTECTED] Eiffestr. 598 20537 Hamburg | Germany Fon 040 | 21 11 05 25 Fax 040 | 21 11 05 26 ___ 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] NameError: Zope2.3a2 and LoginManager-0-8-8b1
Hello, I try to install LoginManager on a new Zope2.3. I have made the before mentioned changes regarding Super and the product shows up fine in the Product folder. But I can not add a LoginManager in a normal folder with the attached error message. I have seen, others have already LoginManager running. Any ideas, where I can look for a clue? TIA, __Janko Error Type: NameError Error Value: path Traceback (innermost last): File /home/zope/LOCAL/zope/lib/python/ZPublisher/Publish.py, line 222, in publish_module File /home/zope/LOCAL/zope/lib/python/ZPublisher/Publish.py, line 187, in publish File /home/zope/LOCAL/zope/lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook File /home/zope/LOCAL/zope/lib/python/ZPublisher/Publish.py, line 171, in publish File /home/zope/LOCAL/zope/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: addLoginManager) File /home/zope/LOCAL/zope/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: addLoginManager) File /home/zope/LOCAL/zope/lib/python/App/special_dtml.py, line 127, in __call__ (Object: addLoginManager) File /home/zope/LOCAL/zope/lib/python/DocumentTemplate/DT_String.py, line 538, in __call__ (Object: addLoginManager) File /home/zope/LOCAL/zope/lib/python/DocumentTemplate/DT_In.py, line 646, in renderwob (Object: UserSourcesMetaTypes(this())) File /home/zope/LOCAL/zope/lib/python/DocumentTemplate/DT_Util.py, line 330, in eval (Object: UserSourcesMetaTypes(this())) (Info: UserSourcesMetaTypes) File /home/zope/LOCAL/zope/lib/python/ZPublisher/HTTPRequest.py, line 802, in __getitem__ NameError: (see above) ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Mapping tools with Zope
GIS-like applications are definitely a field where Zope can shine. But most of the current MAP-Servers are interfacing with a RDBMS where a lot of the logic is placed into the database. If one thinks of geographic objects in a way of an object database like Zope, there is a different architecture needed. For example I think of a RTree indexing technic for the objects stored in the ZODB. This would open a lot of possibilities and would cure one of the problems of current GIS , where everything needs to be stored with a geographical view, which makes it sometimes cumbersome to store legacy information or data with a non gis semantic in these systems. On top of the RTree index one could build a python framework to present the geographical part of this data. These are just thoughts from an earth scientist, who needs to deal with this problem, and is in search for a solution. __Janko -- Institut fuer Meereskunde phone: 49-431-597 3989 Dept. Theoretical Oceanographyfax : 49-431-565876 Duesternbrooker Weg 20email: [EMAIL PROTECTED] 24105 Kiel, Germany ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
