February 2001 - Zope-Dev

problems with LoginManager and proxies
by Tim McLaughlin 12 Feb '01

12 Feb '01

thanks to the excellent tool (tcpwatch) I was able to pinpoint the issue I am having with LoginManager. It seems that it is returning an HTTP/1.0 500 Internal Server Error as the response to the proxy which then tells the browser that the page is a no go (despite the fact that the login page follows as the content). So the browser displays the error message page we all know too well without the content: HTTP 500 - Internal server error Internet Explorer This does not happen it seems when the page is viewed without a client proxy (tcpwatch or other). Note: this request is actually double proxied - I have an Apache reverse proxy setup. Is this problem an Apache issue, or a Zope issue? Please help.... TIA, and beaucoup thanks on the previous question. Tim McLaughlin

2 1

zpopyda problems with typecasting
by Tim McLaughlin 12 Feb '01

12 Feb '01

Timestamp columns do not seem to be converted to DateTime objects in Zope when used with 2.2.4 and PoPy 1.4.1 and ZPoPyDA 1.0.1. It returns a string object which will not convert to a DateTime without some help. The string returned is this '2001-01-24 21:52:19-05' which does not convert because of the -05 zone at the end. Also note, numerics do not seem to be converted to floats either (they are returned as strings but _.float() successfully). Am I just missing something? Tim

1 0

RE: [Zope-dev] Greedy except clauses
by Tom Jenkins 12 Feb '01

12 Feb '01

> -----Original Message----- > From: Jeremy Hylton [mailto:jeremy@digicool.com] > Sent: Saturday, February 10, 2001 1:49 AM > To: Chris Withers > Cc: Anthony Baxter; Chris McDonough; richard(a)bizarsoftware.com.au; > zope-dev(a)zope.org > Subject: Re: [Zope-dev] Greedy except clauses > > > >>>>> "CW" == Chris Withers <chrisw(a)nipltd.com> writes: > > >> I am probably a bit idiosyncratic, but I prefer to avoid bare > >> excepts at all costs. I often use "except Exception:", otherwise > >> I add a > > CW> Will that catch string exceptions? eg: raise 'Something bad > CW> happened' > > No. > > CW> If not, then it's not much use in Zope, which is unfortunately > CW> riddled with String exceptions :-S > > That might be something worth fixing, too. :-) > > Jeremy > I agree. I think this would be a good project for new zope developers to get into the zope code. Would we need an ZopeException class hierarchy? Anthony: can your script be modified to print out the raise statements too <wink>? -------------------------------------------- Tom Jenkins |<xml>Its devIS - Development InfoStructure |all you 703.525.6485 tjenkins(a)devis.com |need it http://www.devis.com |to be</xml>

2 1

InterbaseStorage, Win32 anyone?
by Phil Harris 12 Feb '01

12 Feb '01

Hi all, I'm trying to get InterbaseStorage working on Win32. I've got all the requisite parts and they all seem to be working OK (well, kinterbasdb and mxDateTime do) outside Zope in plain Python. When I try and import _kinterbasdb.dll, from within Zope I'm getting an error message: Unable to initialize mxDateTime Traceback (innermost last): File "D:\Zope230b2\z2.py", line 565, in ? exec "import "+MODULE in {} File "<string>", line 1, in ? File "D:\Zope230b2\lib\python\Zope\__init__.py", line 113, in ? m=imp.load_module('Zope.custom_zodb', m[0], m[1], m[2]) File "D:\Zope230b2\custom_zodb.py", line 1, in ? from Products.InterbaseStorage.InterbaseStorage import InterbaseStorage File "D:\Zope230b2\lib\python\Products\InterbaseStorage\InterbaseStorage.py", line 94, in ? import kinterbasdb File "D:\Python\Lib\kinterbasdb.py", line 4, in ? import _kinterbasdb AttributeError: mxDateTimeAPI Obviously (to me), since Zope has it's own DateTime module, kinterbasdb is looking there for something and not finding what it expects. I've tried monkeying with the Python path to resolve it, but even when it's searching in the right place I'm still getting the error, so I'm at a loss. Has anyone else tried this, and did you get any joy? Is anyone else using mxDateTime (I think it's a pre-requisite of mxODBC)? I've seen one other post about the exact same problem, but with no resolution. Anyone got any ideas? Phil phil.harris(a)zweb.co.uk

2 2

Re: [Zope-dev] Introducing ZopePrints.
by Tres Seaver 12 Feb '01

12 Feb '01

Erik Enge <erik(a)esol.no> wrote: > Some of us over at ZopeZen.org (<URL:http://www.zopezen.org>) have > been discussing the fenomena that is called ZopePrints. I'll give a > brief explanation, and would appretiate feedback as to whether this a > good idea or not. > > A ZopePrint is a document, or maybe a set of documents, which > describes a part of, or the complete development process for a Zope > application. This could include the whole process from when the > customers tell you they want to do project X with you, till you > actually finish it and it's up and running in the customers offices. > > Some points may be: > > * Problem definition > * Problem analysis > * Project management (Resource allocation) > * Design phase > * Zope design > * Test phase > > (Have a looksy at > <URL:http://www.zopezen.org/SDot/981475769/index_html> to check out > all the suggestions, and my initial post.) > > The rationale behind this is that the community at large would benefit > from this by having _real_life_ case studies so when their time has > come to implement an application in Zope, they don't fall into the > same traps and pitfalls we did. Instead of benchmarks, the Zope > community would use implementation documents to decide whether Zope is > up for the job or not, that's what really helps. > > I'm quite sure that it will also work as a tool for finding gaps and > holes in either Zope or its tools and Products. > > We would like to start a project going in the Fishbowl which aims at > creating the right tools to document a project as described above. > > Feel free to make suggestions! Funny you should mention that :) We have been working on just such a site, using the PTK^H^H^HCMF as a tool for managing its own project artifacts. We are calling the project the "CMF dogbowl", as it is a cross between the Fishbowl process and the "eat your own dogfood" mantra made famous by the Mozilla team. Please see: http://dev.zope.org/Projects/PTK for our work-in-progress. Note that this is a separate Zope instance from the rest of 'dev', and that your existing zope.org membership is not (yet) valid there. Tres. -- =============================================================== Tres Seaver tseaver(a)digicool.com Digital Creations "Zope Dealers" http://www.zope.org

2 2

RE: [Zope-dev] Persistence ( was Thread Safe Counting )
by Tres Seaver 12 Feb '01

12 Feb '01

Jon Franz <jfranz(a)one.net> wrote > Ah! this makes more sense, the idea of persistent properties even > fits with this idea, though a true write-in-place property might be > even better for some applications ;) Two things: * Don't count on storing the hit counter as a separate, "persistence aware" object (i.e., with its own pickle jar) to avoid bloating your Data.fs. Hit counters are by definition high volume, and the space overhead for managing undoable persistence is higher than you might think. * Write-in-place will never be supported by packable/undoable storages (logically impossible); some "packless" storages are already in play (maybe even near release), so the semantics you want may be (soon) readily available by mounting a separate storage. Tres. -- =============================================================== Tres Seaver tseaver(a)digicool.com Digital Creations "Zope Dealers" http://www.zope.org

1 0

manage_ methods
by Jon Franz 12 Feb '01

12 Feb '01

Nope! the method calling the manage_* method can have proxy roles setup for it so that it can call manage_* methods for users who do not have the capability to call that manage_* method. Also, any user can be assigned access to the manage_* methods needed on a particular document/method/object by giving them the rights do what you need to do, such as the Change Properties and Add properties rights (might also need the manage_properties right, but I dont think so) via the security tab inside Zope... did this help? >Hi again, > >Is it true that you have to have the Manager role to use any methods that start >with manage_? > >If so, that's pretty unhelpful, almost as unhelpful as the DocString limitation >:-( > >cheers, > >Chris

5 12

Re: [Zope-dev] Greedy except clauses
by Anthony Baxter 12 Feb '01

12 Feb '01

Ok, my last for tonight - I put the output of my horrible script at http://www.zope.org/Members/anthony/BarewordExcepts I'll work over it a bit probably early next week - an obviousish next step is to make it note when the body of the except: contains a 'raise' statement. Anthony

3 2

RE: [Zope-dev] Persistence ( was Thread Safe Counting )
by Jon Franz 11 Feb '01

11 Feb '01

Ah! this makes more sense, the idea of persistent properties even fits with this idea, though a true write-in-place property might be even better for some applications ;) Next time I'll read the whole thread and not the last post in it! > -----Original Message----- > From: Chris Withers [mailto:chrisw@nipltd.com] > Sent: Sunday, February 11, 2001 1:05 PM > To: Jon Franz > Cc: 'zope-dev(a)zope.org' > Subject: Re: [Zope-dev] Persistence ( was Thread Safe Counting ) > > > Jon Franz wrote: > > > > So subclassing persistent will avoid changes to the object > being stored and > > roll-backable in the ZODB? > > NO! read the posting again... Subclassing from persistent is > HOW you make things > live in the ZODB. However, objects that subclass Persistent > get their own pickle > jar, and so only make the ZODB grow by the size of themselves > and their > attributes each time they change. In my counter's case, > that's not a lot :-) > > > Now, if only we could get this sort of > > store-in-place functionality on a more fine-grained level (like on > > individual > > properties) - we could avoid a lot of coding to prevent > ZODB bloat with > > simple > > features.. Ie, if I were to make a 'persistent porperty' on > a DTML method, > > I could store counter information in that property without worry > > of ZODB bloat. > > I wouldn't be surprised if something like this happens at > some stage ;-) > > cheers, > > Chris >

1 0

Persistence ( was Thread Safe Counting )
by Jon Franz 11 Feb '01

11 Feb '01

>> Morten's product stores the counter's >> value in a file on the filesystem, and so it doesn't cause the >> Data.fs to grow. > >Hmmm, well, my counter above wouldn't cause the data.fs to grow all that much, >since it subclasses Persistent and so gets its own pickle jar. > >cheers, > >Chris So subclassing persistent will avoid changes to the object being stored and roll-backable in the ZODB? Nice! Now, if only we could get this sort of store-in-place functionality on a more fine-grained level (like on individual properties) - we could avoid a lot of coding to prevent ZODB bloat with simple features.. Ie, if I were to make a 'persistent porperty' on a DTML method, I could store counter information in that property without worry of ZODB bloat. Hrm... *Jon staes into the distance wondering how much will break if he tries to implement a 'persistent' flag for properties* ~Jon

2 1