- Zope-Dev - Zope lists

How to map Zope with IIS 5.1
by Rohit Arora 04 Feb '07

04 Feb '07

hi all i have a website in zope 2.6.4 , and i want to link that website with IIS 5.1. in other words, i have created a virtual directory in IIS and i want to redirect the request to zope website. so i need to access my Zope website after passing through IIS 5.1 please tell me how to map zope with IIS, Very Urgent thanks rohit -- View this message in context: http://www.nabble.com/How-to-map-Zope-with-IIS-5.1-tf3162485.html#a8772316 Sent from the Zope - Dev mailing list archive at Nabble.com.

2 1

Re: ploneenv - Or how using workingenv for a common Zope2 project might look like ;-)
by Ian Bicking 04 Feb '07

04 Feb '07

Daniel Nouri wrote: [...] >> - There is a single file that shows me what eggs and development eggs >> make up my package. This makes it easy to add new eggs, for example - >> and also easy to remove them again. With workingenv-based solutions, you >> can specify a file full of eggs to install when it's first set up, but >> from that point onwards, the environment can grow as you easy_install >> new things. It's not immediately clear to me how you reconcile all the >> eggs you've installed (not all of which may be needed when you're done >> trying things out, and some of which may just be dependencies you don't >> want to think about directly) into a list that are clearly dependencies >> of your application. > > Querying the list of installed eggs is what tools like Yolk[5] are good for. > Note that for setuptools packages, the setup.py file lists all > dependencies. If you develop for e.g. Listen and Plone, you only need to > keep track of Listen and Plone. One of the things that I think is pretty easy with workingenv, and a bit confusing with buildout, is moving one package into development. In workingenv you get the package you want (however you do that -- check out a branch, make your own local repository, unpack a tarball, etc), and you run (after activating the environment) "python setup.py develop". Or if the package isn't using setuptools, "python -c 'import setuptools; execfile("setup.py")' develop". Note that this is actually one of the few places you actually have to activate the environment. And heck, if I just compiled a little something into bin/python then even that wouldn't be necessary. (Maybe even a hard link would be enough, I'm not sure.) In buildout it's a bit more complicated. You can move an egg into develop-eggs, but that relies on buildout finding the right package. That's not really that easy, especially because setuptools only really understands packages being newer or older, it doesn't understand things like branches. It's hard even when you don't have this problem. >> - With workingenv, when I run easy_install SomePackage I need to worry >> about whether I'm actually in the global environment or the workingenv >> of the instance. That is, workingenv requires activation (putting your >> shell into a special state where the python environment is the one in >> your workingenv, until you deactivate it). By contrast, other people may >> not like the "add to buildout.cfg, re-run buildout dance" that buildout >> uses instead. If you use the easy_install script in the workingenv bin/, then you don't have to activate the environment. Very similar to buildout, workingenv scripts contain their path/environment. >> - It works in Windows. :) I have no idea how hard it's to make ploneenv >> work on Windows, but I hope it's not too bad. The scripts Hanno wrote do >> give us a near-proper zopectl for Windows as well, which is nice. I >> imagine these could be adapted to be used with plain Zope instances, >> though. I assume workingenv gives us setuptools script support locally >> as well. > > Support for Windows should be fairly trivial. I would appreciate it if > someone (Hanno?) gave it a try. Basically, all we need is the correct way > to patch bin/zopectl so that it runs the bin/activate.bat script before > startup. We shouldn't seriously consider "runs on Windows" as an argument > for ploneout, just because ploneenv hasn't seen a Windows developer yet. :-) Workingenv does, as far as I know, work with Windows. At least I've received several patches (I've never used it myself). -- Ian Bicking | ianb(a)colorstudy.com | http://blog.ianbicking.org

3 2

Zope Tests: 7 OK
by Zope Tests Summarizer 04 Feb '07

04 Feb '07

Summary of messages to the zope-tests list. Period Sat Feb 3 12:00:00 2007 UTC to Sun Feb 4 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Sat Feb 3 21:05:04 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007181.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Feb 3 21:06:34 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007182.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Feb 3 21:08:04 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007183.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Feb 3 21:09:34 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007184.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 3 21:11:04 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007185.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 3 21:12:34 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007186.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 3 21:14:04 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007187.html

1 0

Zope Tests: 7 OK
by Zope Tests Summarizer 03 Feb '07

03 Feb '07

Summary of messages to the zope-tests list. Period Fri Feb 2 12:00:00 2007 UTC to Sat Feb 3 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Fri Feb 2 21:04:49 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007174.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Feb 2 21:06:19 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007175.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Feb 2 21:07:50 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007176.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Feb 2 21:09:20 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007177.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Feb 2 21:10:50 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007178.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Feb 2 21:12:25 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007179.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Feb 2 21:13:55 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007180.html

1 0

undeprecating zLOG
by Chris McDonough 03 Feb '07

03 Feb '07

How many people would get indignant if I checked in a fix that undeprecated zLOG? Removing the API seems silly, since its just a wrapper around the logging module now anyway. - C

7 14

Zope Tests: 7 OK
by Zope Tests Summarizer 02 Feb '07

02 Feb '07

Summary of messages to the zope-tests list. Period Thu Feb 1 12:00:00 2007 UTC to Fri Feb 2 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:09:11 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007167.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:10:41 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007168.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:12:11 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007169.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:13:41 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007170.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:15:11 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007171.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:16:41 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007172.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Feb 1 21:18:11 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-February/007173.html

1 0

Zope Tests: 7 OK
by Zope Tests Summarizer 01 Feb '07

01 Feb '07

Summary of messages to the zope-tests list. Period Wed Jan 31 12:00:00 2007 UTC to Thu Feb 1 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Wed Jan 31 21:07:35 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007160.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Jan 31 21:09:05 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007161.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Jan 31 21:10:35 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007162.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Jan 31 21:12:05 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007163.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jan 31 21:13:35 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007164.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jan 31 21:15:05 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007165.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jan 31 21:16:35 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007166.html

1 0

[German Zope Conference] Call for Papers open
by Andreas Jung 01 Feb '07

01 Feb '07

Dear Zope Community, the eighth Zope conference organized by the German Zope User Group (DZUG) will be held this year at the Potsdam Institute for Climate Impace Research from 4. to 5 June 2007 (near Berlin). The topic of the conference will be Zope in sciences. Proposals for talks and workshops can be submitted until 01.04.2007 http://www.zope.de/redaktion/dzug/tagung/potsdam-2007/dzug-conference-2007-… or http://www.zope.de/redaktion/dzug/tagung/potsdam-2007/dzug-conference-2007-… Both German and English proposals are highly welcome. You can find further information about the Zope conference here: http://www.zope.de/8-dzug-tagung Regards, Andreas Jung Assistant Chairman DZUG e.V. -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 E-Publishing, Python, Zope & Plone development, Consulting

1 0

RFC: Eggifying Zope's extension mechanism ("Products")
by Philipp von Weitershausen 31 Jan '07

31 Jan '07

For their upcoming versions, Zope 2 consuming platforms such as Plone are creating standard Zope3-style Python packages while still having Zope 2 products around. This proposal aims at unifying the deployment of products and Python packages into a Zope 2 instance alike by using Python eggs and their entry point system. See http://wiki.zope.org/zope2/EggifyingZopesExtensionMechanismQuotProductsQuot for the full proposal. Comments are appreciated. I plan on implementing it at the Camp5 BBQ sprint (http://www.openplans.org/projects/bbq-sprint) -- http://worldcookery.com -- Professional Zope documentation and training Next Zope 3 training at Camp5: http://trizpug.org/boot-camp/camp5

5 10

Zope Tests: 7 OK
by Zope Tests Summarizer 31 Jan '07

31 Jan '07

Summary of messages to the zope-tests list. Period Tue Jan 30 12:00:00 2007 UTC to Wed Jan 31 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Tue Jan 30 21:07:01 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007153.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 30 21:08:31 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007154.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 30 21:10:01 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007155.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 30 21:11:31 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007156.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 30 21:13:01 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007157.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 30 21:14:31 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007158.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 30 21:16:02 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007159.html

1 0