J Cameron Cooper wrote:

Rod Thorburn wrote:

...

I am running Zope 2.6.3 (binary release) on win2k, which by default installs Python 2.1.3 . However, I wish to use Python 2.3.3 and I can't see how to 'swap' Python instances.

You can call whatever version of Python you want to use when starting Zope. The binary release of that version makes a 'start' script that calls the Python binary that comes with it. You can edit that script to use whatever version of Python you like to execute 'z2.py'. (I usually make it call a symbolic link that I can change to point at different Python executables without editing the script.)

Zope 2.6.x may or may not work well with Python 2.3.3. Zope 2.7 is the release that officially goes to Python 2.3 series. It has a slightly different scheme for starting, as I recall.

--jcc

Is this true? Zope does use compiled c programs which must be linked to the correct Python version. Robert

robert rottermann wrote:

J Cameron Cooper wrote:

...

Rod Thorburn wrote:

...

I am running Zope 2.6.3 (binary release) on win2k, which by default installs Python 2.1.3 . However, I wish to use Python 2.3.3 and I can't see how to 'swap' Python instances.

You can call whatever version of Python you want to use when starting Zope. The binary release of that version makes a 'start' script that calls the Python binary that comes with it. You can edit that script to use whatever version of Python you like to execute 'z2.py'. (I usually make it call a symbolic link that I can change to point at different Python executables without editing the script.)

Zope 2.6.x may or may not work well with Python 2.3.3. Zope 2.7 is the release that officially goes to Python 2.3 series. It has a slightly different scheme for starting, as I recall.

--jcc

Is this true? Zope does use compiled c programs which must be linked to the correct Python version.

Oops. You're right. I guess I never actually switch versions that way. Yes, one would also have to run the build script with the target Python, as well. --jcc -- "My point and period will be throughly wrought, Or well or ill, as this day's battle's fought."

Hi all. Is there a way to mount an OS directory (*nix/Windows) as a Zope database? I've done lots of Googling for an answer, but no results yet so I thought I'd ask here. We use Zope on Mandrake Linux at my company and a lot of our developers prefer to use Vi to edit files, and absolutely hate using the web interface to edit files (debugging hell). WebDAV is not totally out of the question, but we all think it would be cool if you could mount a directory as a Zope DB. Anyway, if there is no current way to do this, I'm considering writing it myself. Let me know what you all think. James Cammarata jimi@sngx.net www.sngx.net home: 314-835-1122 work: 314-872-2426 cell: 314-409-0583 ______________________________________________________________ Out the Ethernet, through the router, down the fiber, off another router, down the T1, past the fire-wall ...nothing but Net

Hello

We use Zope on Mandrake Linux at my company and a lot of our developers prefer to use Vi to edit files, and absolutely hate using the web interface to edit files (debugging hell).

When you need it only for programming reasons, have a look at http://boa-constructor.sourceforge.net/. Regards Dieter

James Cammarata wrote:

Hi all. Is there a way to mount an OS directory (*nix/Windows) as a Zope database? I've done lots of Googling for an answer, but no results yet so I thought I'd ask here.

We use Zope on Mandrake Linux at my company and a lot of our developers prefer to use Vi to edit files, and absolutely hate using the web interface to edit files (debugging hell). WebDAV is not totally out of the question, but we all think it would be cool if you could mount a directory as a Zope DB.

Anyway, if there is no current way to do this, I'm considering writing it myself. Let me know what you all think.

Depending on what you're doing, you may want to look at APE or LocalFS or FileSystemSite. LocalFS is mostly for content, FSS (and, similarly, CMF skins) is mostly for templates and scripts, and APE is for everything. LocalFS and FSS make filesystem stuff available in Zope's object tree. APE stores the objects on the filesystem. (There's a real difference, but they're very much equivalent.) APE is probably the most difficult to set up. There are some other options that mostly deal with individual files (ExtFile, External File) or with storing the ZODB in non-editable format (DirectoryStorage). But I find that most of your real work should probably be done in filesystem-side products anyway, and anything that's ZODB-resident is really glue and shouldn't be complex enough that editing in a text box is a serious hindrance. --jcc -- "He who fights with monsters should look to it that he himself does not become a monster. And when you gaze long into an abyss the abyss also gazes into you."