Re: [Zope-dev] Retracting Zope 2.9.7, Zope 2.10.3 releases because of a "zopectl start" problem

According to Andreas Jung: > I decided to retractthe latest 2.9.7 and Zope 2.10.3 releases > for now because of this problem: > > > > I could confirm that "zopectl start" does not work properly. > zdaemon spawns the second process howev

Re: [Zope-dev] 2.9.4? reStructuredText support?

According to Andreas Jung: > >> Tres' patch is looking in fine to me. I don't see a need right now > >> for dropping reST with having file inclusing *removed*. > > > > Has anyone written tests for Tres' patch? Apparently no one wrote > > adequate tests for the last hot fix, which helped put us in

Re: [Zope-dev] Re: xmlrpc OverflowError fault

According to Tres Seaver: > > Trying to get a Zope DateTime object (as dictionary value) via xml-rpc > > gives on OverflowError! You can try it yourself: > > > > (I used a freshly installed Zope-2.9.3 [with python-2.4.3] on Linux > > FC3; but other versions should behave equally.) > > > > Add a P

[Zope-dev] xmlrpc OverflowError fault

Trying to get a Zope DateTime object (as dictionary value) via xml-rpc gives on OverflowError! You can try it yourself: (I used a freshly installed Zope-2.9.3 [with python-2.4.3] on Linux FC3; but other versions should behave equally.) Add a Python Script in the Zope OFS root folder: return {'

Re: [Zope-dev] Please vote about conflict errors logging

Florent Guillaume wrote at 2005-12-2 23:00 +0100: >Please vote for the level at which you want to log retried conflict >errors. These are the ConflictErrors that aren't returned to the user >but automatically retried by the Zope publisher. > >1. Do you want these ConflictErrors retried logs to

Re: [Zope-dev] XML Export Error and Patch

According to Dieter Maurer: > Willi Langenberger wrote at 2004-11-10 23:28 +0100: > > ... > >The following patch (implement "extend" like "append") solves the problem > >(for me!): > > Please file a bug report with solution to > >

[Zope-dev] XML Export Error and Patch

Hi! When i try to export a PluggableAuthService object as XML, (with ZMI Import/Export or with manage_exportObject?id=acl_users&download=1&toxml=Y) i get the following exception: Error Type: AttributeError Error Value: List instance has no attribute 'extend' [...] Traceback (innermost

Re: [Zope-dev] Re: Developing plugins for PluggableAuthService

According to Chris Withers: > Is there any chance I could tempt you to change these to be Python 2.3 > style logging calls? Zope will be moving to them for 2.8 and it'd be > great if you can change the code while you're "in there"... Do you have an example at hand? I remember a posting to this l

Re: [Zope-dev] Re: Developing plugins for PluggableAuthService

According to Chris Withers: > Could you add this patch to the following collector issue: > > http://zope.org/Members/urbanape/PluggableAuthService/Collector/4 Sure! (i didnt do it in the first place, because it was already in CVS -- but you are right, it should be in the collector) \wlang{} -

Re: [Zope-dev] Re: Developing plugins for PluggableAuthService

According to Lennart Regebro: > No. Closer inspection seems to show that I actually don't get PAS to do > anything at all. It is simply ignored, unless I put it into the root, in > which case I can't do anything, since it doesn't care of emergency_user. I also had this problem with the emergency

Re: [Zope-dev] Segfault and Deadlock

According to Dieter Maurer: > >The reason is the way python handles threads on some systems > >(RedHat-7.3, kernel 2.4.20, without NPTL). > > What is "NPTL"? Native POSIX Thread Library. > That is the good behaviour. Thus, we only have to learn > how we can get "NPTL" for all Linux systems. How

[Zope-dev] Segfault and Deadlock

Hi Zope (and Python) experts! There seems to be a problem when an external python module segfaults during a zope request. The remaining worker threads are deadlocked. I think this is the same problem as Dieter pointed out in his message to zope-dev "[Problem] strange state after SIGSEGV": http

Re: [Zope-dev] zope 2.7.0: no tracebacks produced

According to Mika, David P (Research): > I am making a big upgrade and moving my products from 2.3.1 on HP-UX > to 2.7.0 on windows 2000 and can't get zope to produce any tracebacks > when it encounters errors. I've checked all the log files and monitor > stdout > to no avail. All I get is a b