July 2004 - Zope-Dev

Access Zope objects from python
by Tor Oskar Wilhelmsen 06 Jul '04

06 Jul '04

Hi This question is from a Zope newbie, who gets a little confused when trying to write a product for Zope. My product fetches a lot of picture information, and this information shall be viewed in a fotogallery (the viewer is made as a ZPT) My question is really simple then: When I write this product in python, how could I generate a zope image object of each of the pictures in the db. The part I am interested in is how I can access and create zope objects from python. Which classes do I have to inherit from? -Tor Oskar Wilhelmsen

2 1

Re: [Zope-dev] Zope 2.7.0 and Pythom Image Library
by Tor Oskar Wilhelmsen 05 Jul '04

05 Jul '04

That was my thought to, but it isn't like that. When I run the code from command line, all works perfectly well. The difference in the command line vs zope is that in the command line the from OFS import SimpleItem is ignored, and I use the class gallerybase: instead of #class gallerybase(SimpleItem.Item): Can the import of SimpleItem, and the inheritance of SimpleItem.Item make som errors?? -TOW ----- Original Message ----- From: "Andreas Jung" <ajung(a)zopyx.com> To: "Tor Oskar Wilhelmsen" <toroskar(a)chello.no>; <zope-dev(a)zope.org> Sent: Monday, July 05, 2004 8:33 AM Subject: Re: [Zope-dev] Zope 2.7.0 and Pythom Image Library > If the code works in pure Python then it must work in Zope especially when > you call > the code from an external method or other filesystem-based code as long as > you are using > the same Python version. Your problem looks likely that your input data is > broken. > > -aj > > --On Montag, 5. Juli 2004 8:27 Uhr +0200 Tor Oskar Wilhelmsen > <toroskar(a)chello.no> wrote: > > > Hi > > I'm trying to get the PIL(last version on python 2.3) working with Zope, > > but it seems that it's not working. > > > > I use the code: > > file = StringIO.StringIO(data) > > im = Image.open(file) > > im.show() > > > > where data is datafrom a blob in a db. This code is working outside > > Zope, but at once when i try to make it a product in Zope, I get this > > error: > > > > IOError: cannot identify image file > > > > > > Does anyone know what's wrong or what to do to make this work? > > > > Thanks for all help! > > > > > > Regards > > Tor Oskar Wilhelmsen > > > > Andreas Jung > zopyx.com - Software Development and Consulting Andreas Jung

1 0

INSTANCE_HOME and SOFTWARE_HOME still necessary in 2.7 start script?
by Chris Withers 03 Jul '04

03 Jul '04

Hi there, Is it still necessary to specify INSTANCE_HOME and SOFTWARE_HOME in the start script for Zope? Or would the following work? python /my/path/to/Zope/startup/run.py -C /my/instance/path/zope.conf cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 4

Who's experiencing FileStorage corruption?
by Tim Peters 01 Jul '04

01 Jul '04

[follow-ups to zodb-dev(a)zope.org, please] We (Zope Corp) occasionally get reports of FileStorage (Data.fs) corruption of kinds that aren't understood, and that are never seen in Zope Corp's own Zope deployments, neither in extreme artificial stress tests. We take corruption very seriously, and there are no known bugs in the current releases of ZODB that can cause corruption. Therefore we're very keen to investigate cases that may still exist. By "corruption", I mean what corruption conventionally means for any file: the Data.fs and/or Data.fs.index file is damaged at the byte level, as if someone had overwritten some region (or regions) with nonsense bytes. Of course this can be a disaster when it occurs. Visible symptoms may include: + FileStorage.py raises CorruptedDataError. + FileStorage.py passes on this exception from Python's struct module: error: unpack str size does not match format The only currently known causes for these are hardware problems (bad disk, bad disk controller, loose connection, flaky memory chip) and equivalently fatal system software bugs (buggy system disk driver, buggy system I/O libraries, buggy third-party software). If you experience corruption not due to such causes beyond ZODB's control(*), we want to hear about it! The best place to report a case is on the Zope Collector: http://collector.zope.org/Zope with topic "Database". Because database files can be very large, and may contain sensitive data, please don't attach them to the report; you should be willing to let us get copies of them privately, though. (*) How do you know whether the cause is beyond ZODB's control? You probably can't, and that's fine. A case where you can: the last time Jim Fulton tried to track one of these down, the customer's system was in such bad shape that they were unable to make a readable tar file containing their database files: attempts to do so created corrupt *tar* files. If I/O on your system is plain broken, then no, FileStorage isn't going to work either.

1 0