November 2006 - Zope

error with simple python script loop
by Christian Steinhauer 24 Nov '06

24 Nov '06

I have an problem with this little script. The script is in the zope file structure and it is an -Script (Python)- The script should send 2 emails over the mailhost, but it sends 4 emails. I have test this with maildrophost product too, same problem. I have test it on Zope 2.10.0 and Zope 2.64. The problem is the same - everytime. This script produce the error: #### start #### for i in range(2): subj = str(i) + ' range python' context.MailHost.send('range test with python', "rec(a)mail.com", "sender(a)mail.com", subj) #### end #### This script produce no error: #### start #### for i in range(2): subj = str(i) + ' range python' context.MailHost.send('range test with python', "rec(a)mail.com", "sender(a)mail.com", subj) return 'eof' #### end #### So if i make a return (not in the loop) the script works fine. Can anybody tell me why? It feels like that there are any spaces in the script and zope/python did not work correctly when there is no other procedure after the for loop. I dont understand why he calls the loop two times and produce 4 emails. There is no transactional error in the error_log. thx for help

5 4

Re: [Zope] error with simple python script loop
by Jonathan 24 Nov '06

24 Nov '06

----- Original Message ----- From: "Christian Steinhauer" <steinhauer(a)know-it.net> To: "Jonathan" <dev101(a)magma.ca>; <zope(a)zope.org> Sent: Friday, November 24, 2006 8:19 AM Subject: Re: [Zope] error with simple python script loop >>>I just cut and pasted your code into a python script on my >>>Zope installation >>>(2.9.2) and it worked as expected (ie. 2 emails sent). So >>>something is >>>pooched in your installation. >>> >>>A quick way to check to see if your script is looping more >>>than you expect >>>is to do something like: >>> >>>loopCheck = [] >>>for i in range(2): >>> subj = str(i) + ' range python' >>> context.MailHost.send('range test with python', "rec(a)mail.com", >>>"sender(a)mail.com", subj) >>> loopCheck.append(subj) >>>return loopCheck >>> >>>If you are getting only 2 iterations of the loop (as it >>>should be), then >>>something is wrong with your MailHost (if this is the case >>>try deleting it >>>and re-adding it). Another test: place a local copy of >>>MailHost in the same >>>folder as your script and see what happens. > > Hi Jonathan, thanks for taking care of the problem. I have done the self > test you do with the list. But everytime when something is written at last > line, example return 'eof' (My example in the topic) the error did not > occured - so the list gives me 2 and i will get 2 emails. > > The error only occured when nothing is written under the loop. > > I have 2 real separeted dedicated servers, one with zope 2.6.4 and one > with 2.10 - the problem occured on both servers. > So i used the zope product "MailDropHost" too and get the self error on > both server. With MailDropHost i can see a spooler - thats nice - but in > the spooler i see 4 emails. So the Operating System or Exim get 4 Mails > from Zope/Python. > I´m using Debian Linux. I tried to reproduce your '4 iteration' problem on my Zope 2.9.2 installation, but even by removing the 'return' statement I still got 2 loop iterations (and 2 emails). I have never written a python script that did not have a 'return' statement. I don't know if it is mandatory or not. I usually use python scripts as subroutines/functions and I always have a return statement (even if it is a bare return - ie. the return statement does not send back any data). As Andreas suggested, if you want to track this down you are going to have to use a debugger like pdb. Jonathan

2 1

Re: [Zope] error with simple python script loop
by Christian Steinhauer 24 Nov '06

24 Nov '06

>>I just cut and pasted your code into a python script on my >>Zope installation >>(2.9.2) and it worked as expected (ie. 2 emails sent). So >>something is >>pooched in your installation. >> >>A quick way to check to see if your script is looping more >>than you expect >>is to do something like: >> >>loopCheck = [] >>for i in range(2): >> subj = str(i) + ' range python' >> context.MailHost.send('range test with python', "rec(a)mail.com", >>"sender(a)mail.com", subj) >> loopCheck.append(subj) >>return loopCheck >> >>If you are getting only 2 iterations of the loop (as it >>should be), then >>something is wrong with your MailHost (if this is the case >>try deleting it >>and re-adding it). Another test: place a local copy of >>MailHost in the same >>folder as your script and see what happens. Hi Jonathan, thanks for taking care of the problem. I have done the self test you do with the list. But everytime when something is written at last line, example return 'eof' (My example in the topic) the error did not occured - so the list gives me 2 and i will get 2 emails. The error only occured when nothing is written under the loop. I have 2 real separeted dedicated servers, one with zope 2.6.4 and one with 2.10 - the problem occured on both servers. So i used the zope product "MailDropHost" too and get the self error on both server. With MailDropHost i can see a spooler - thats nice - but in the spooler i see 4 emails. So the Operating System or Exim get 4 Mails from Zope/Python. I´m using Debian Linux.

2 1

Re: [Zope] error with simple python script loop
by Christian Steinhauer 24 Nov '06

24 Nov '06

>>As I said in the tracker, no one can help you if you don't >>actually give us the full traceback and exception that you got. There is no traceback, i got no error - thats why i have post it into bug tracker. I spoke to many people but no one can tell me why it occured. The most said that it must be a bug in zope or python. @Maciej: I call the script simple over url or the "test" button - it is a script for testing only - it is not called by any other script

2 1

Specifying the target language with i18n
by Daniel de la Cuesta 24 Nov '06

24 Nov '06

Hello, I am trying to set the target language using "i18n:target" label Example: <p i18n:translate="" i18n:target="string:en"> label_search </p> It doesn't work. I cannot specify the target language. I am in Zope 2.9.4. Thank you. ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com

2 2

Re: [Zope] Re: Specifying the target language with i18n
by Daniel de la Cuesta 24 Nov '06

24 Nov '06

It is not necesary. Anyway, if I specify my domain nothing happens. ----- Mensaje original ---- De: Josef Meile <jmeile(a)hotmail.com> Para: zope(a)zope.org Enviado: viernes, 24 de noviembre, 2006 13:03:31 Asunto: [Zope] Re: Specifying the target language with i18n Hi Daniel, > Hello, > > I am trying to set the target language using "i18n:target" label > > Example: > > <p i18n:translate="" i18n:target="string:en"> > label_search > </p> > > It doesn't work. I cannot specify the target language. > > I am in Zope 2.9.4. Just a guess: Don't you need to specify a domain as well? Regards Josef _______________________________________________ Zope maillist - Zope(a)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 ) ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com

1 0

[Fwd: Re: [Zope] help performance]
by Yuri 24 Nov '06

24 Nov '06

Martijn Pieters wrote: > On 11/24/06, Yuri <yurj(a)alfa.it> wrote: >> > and *enable* subtransactions! >> >> When I have a transaction wich takes almost 1 sec, I don't think it will >> change anything :) I'll try CallProfiler :) > > Did you try? Subtransactions are not the same as transactions. They > are an optimization, so try them! Don't just ditch the experts here. > 0.0209 0.9% | +0.0209 0.0174 0.7% +- inserimento +0.0320 0.0042 0.2% | +- standard_html_header +0.0337 0.0017 0.1% | | +- intestazione_html_standard +0.0374 0.0011 0.0% | | +- mappa_barra_loggato +0.0423 1.0951 46.8% | +- dafne_item_add 0.5836 24.9% | | | +0.6260 0.0028 0.1% | | +- proprietario +0.6301 0.0484 2.1% | | +- sonopubblico +0.6804 0.0026 0.1% | | +- proprietario (2nd call) 0.0406 1.7% | | | +0.7236 0.0043 0.2% | | +- globale 0.4665 19.9% | | | +1.1945 0.0457 2.0% | | +- sonopubblico (2nd call) +1.2423 0.0033 0.1% | +- invalida_cache +1.2468 0.0010 0.0% | +- standard_html_footer Ok, I've run a machine for three years without any optimizations. Enabling transaction cut the time of about 73%: http://myurl/inserimento 2.3416 5.5694 8.7971 8.7971, 2.3416 8.7971 was the time without subtransactions, 2.3 with. Ops... -.-

2 2

help performance
by Yuri 24 Nov '06

24 Nov '06

Hi! I've an old machine with zope 2.6 with an application based on ZClass. Now, updating 4000 record takes ages (more than an hour...), basically it is a propertysheet update + recatalog of every object of 4000. Can I have significative performance upgrade changing something in the code base? Some ZCatalog "slow" bug in 2.6 I could patch you know of? :) TIA

5 10

TimeError in Zope 2.8.5
by John McIntyre 23 Nov '06

23 Nov '06

Greetings ~ I have been experiencing a "TimeError" in Zope 2.8.5 instance running on Python 2.3.5. -- Site Error An error was encountered while publishing this resource. Error Type: TimeError Error Value: The time 106900545747.045975 is beyond the range of this Python implementation. -- Here's the traceback... -- TimeError Sorry, a site error occurred. Traceback (innermost last): * Module ZPublisher.Publish, line 113, in publish * Module ZPublisher.mapply, line 88, in mapply * Module ZPublisher.Publish, line 40, in call_object * Module Shared.DC.Scripts.Bindings, line 311, in __call__ * Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec * Module App.special_dtml, line 175, in _exec * Module DocumentTemplate.DT_Var, line 214, in render * Module App.PersistentExtra, line 34, in bobobase_modification_time * Module DateTime.DateTime, line 509, in __init__ * Module DateTime.DateTime, line 760, in _parse_args * Module DateTime.DateTime, line 437, in safelocaltime TimeError: The time 106900545747.045975 is beyond the range of this Python implementation. -- The error is mostly noticed in the ZMI. I can't view a large percentage of pages in the Content frame of the ZMI, including the Root Folder view. It has been a hugely problematic issue for me. This error began when my hosting account was moved from Zettai.net to HighSpeedRails.com. I did not have the error on Zettai. I didn't change anything after my data was moved to HSR that would have caused the error. In trying to solve the issue with HSR, I have been told that the error is coming from my data. I have rather thoroughly checked my data for the time value and have not come up with anything. I spoke to someone who thought, since the error is pervasive and the traceback points to the basic rendering of the object and a system property, I might have no control over it. The TimeError might indicate something with the setup of the hosting environment. - The "time" value is always the same. - I have been told 106900545747.045975 converts to: Tue May 22 1973 01:35:45 GMT-0500. I have learned that DateTime sometimes has issues with dates outside of 1970 - 2038. 1973 should fall within the acceptable range. - When I asked HSR if there was any difference in the way that time is being handled on the new servers that is different from the old servers, I found that my old account was on CST and the new account is on EST. Not sure if that matters or not. - I found the following links pertaining to the TimeError: http://marc.theaimsgroup.com/?l=zope-db&m=109044731701981&w=2 http://mail.zope.org/pipermail/zope-checkins/2003-November/025122.html - I did trace the error back to "safelocaltime" in DateTime.py If anyone knows anything about the TimeError and could pass a few clues my way I would really appreciate it. I'd like to find out how/why the hosting environment handles the dates differently. Thank you very much ~ John McIntyre 612 423 9692 john(a)johnnyflash.com

4 7

CMF-2.1.0-alpha2 released
by Jens Vagelpohl 23 Nov '06

23 Nov '06

The CMF developer community is hereby announcing the release of CMF version 2.1.0-alpha2. This second alpha release was cut to help release Plone 3.0-alpha. A lot of bug fixes and features have made it into the CMF since release 2.1.0-alpha, which has become somewhat obsolete as the basis for Plone 3.0-alpha. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. The CMF provides the foundation for popular software packages such as Plone. It is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? For release files, change logs, installation instructions and more please visit http://www.zope.org/Products/CMF/CMF-2.1.0-alpha2. Roadmap and release information can be found at http://www.zope.org/Products/CMF/docs/roadmap. The CMF mailing list can be reached at the zope-cmf(a)zope.org address, to sign up please visit http://mail.zope.org/mailman/listinfo/zope- cmf. Please file bug reports, feature requests or suggestions in the CMF bug collector at http://www.zope.org/Collectors/CMF . What has changed since the last release? New Features - WorkflowTool: Added the IConfigurableWorkflowTool interface. This change includes the new 'getDefaultChain' and 'listChainOverrides' methods and an improved 'setChainForPortalTypes' method. The import handler now supports the 'remove' attribute for removing overrides. (http://www.zope.org/Collectors/CMF/457) - CMFCore.CachingPolicyManager: Implemented the old OFS.Cache.CacheManager API. Now objects other than CMF content or CMF templates can have their caching headers set by the caching policy manager with the same fine-grained control. (http://www.zope.org/Collectors/CMF/408) - testing: Added test layers for setting up ZCML. - CMFDefault formlib: Added zope.formlib support. This includes some CMF specific base classes and an 'EmailLine' field. - browser views: Added some zope.formlib based forms. - CMFDefault utils: Added 'checkEmailAddress' function. - Added CMFCore.FSRestMethod: ReST equivalent of FSSTXMethod. - CMFCore.FSSTXMethod: Modernized, added tests, made customization possible (now renders via ZPT by default, using 'main_template'). - Portal: Added 'email_charset' property. - CMFDefault utils: Added 'makeEmail' function. - CMFDefault.Image and CMFDefault.File: Overridden index_html methods add Cache Policy Manager-awareness and thus bring these implementations in line with CMFCore.FSFile and CMFCore.FSImage (http://www.zope.org/Collectors/CMF/454) Bug Fixes - CMFCore.CachingPolicyManager: Prevent firing of caching policies for templates (DTML or ZPT) that are rendered in-line (without a separate request) while rendering the requested content item's view. (http://www.zope.org/Collectors/CMF/456) - CMFDefault RegistrationTool: Fixed too restrictive email checking. The new 'checkEmailAddress' function is now used. - Fixed test breakage induced by use of Z3 pagetemplates in Zope 2.10+. - CMFDefault skins: Fixed encoding issues in welcome and reminder emails. 'password_email' and 'registered_email' now encode their return value correctly, using 'email_charset' and the new 'makeEmail' function. Others - The CMF now depends on Zope 2.10.1

1 0