Re: [Zope-dev] Zope 2.12.0 released

2009-10-05 Thread Dragos Chirila
Hi, I have tried to install it on an windows: the egg for python 2.4 works, but the one for 2.6 fails with the following error: Installed d:\pythonfarms\python262\lib\site-packages\zope2-2.12.0-py2.6-win32.egg Processing dependencies for Zope2==2.12.0 Searching for zope.container Reading

Re: [Zope-dev] Zope 2.12.0 released

2009-10-05 Thread Chris Withers
Dragos Chirila wrote: Hi, I have tried to install it on an windows: the egg for python 2.4 works, but the one for 2.6 fails with the following error: This is because there was no 2.6 binary egg. I've just rolled one and uploaded it. Can you try again and let me know how you go? Chris --

[Zope-dev] zope.filerepresentation release

2009-10-05 Thread Martin Aspeli
Hi, Following an earlier discussion on this list, I've made changes to zope.filerepresentation to incorporate two new interfaces, IRawReadFile and IRawWriteFile. These allow file representation adapters which behave like Python standard library 'file' objects. This in turn allows

Re: [Zope-dev] Zope 2.12.0 released

2009-10-05 Thread Andreas Jung
Am 05.10.09 11:49, schrieb Chris Withers: Dragos Chirila wrote: Hi, I have tried to install it on an windows: the egg for python 2.4 works, but the one for 2.6 fails with the following error: This is because there was no 2.6 binary egg. I've just rolled one and uploaded it.

Re: [Zope-dev] Zope 2.12.0 released

2009-10-05 Thread Dragos Chirila
Hi Chris, The installation worked smoothly. Still, I had to modify something in the site-packages\zope\interface\common\interfaces.py file : try: classImplements(OverflowWarning, IOverflowWarning) except NameError: pass # OverflowWarning was removed in Python 2.5 Otherwise, Zope wont

Re: [Zope-dev] Zope 2.12.0 released

2009-10-05 Thread Chris Withers
Dragos Chirila wrote: Hi Chris, The installation worked smoothly. Still, I had to modify something in the site-packages\zope\interface\common\interfaces.py file : try: classImplements(OverflowWarning, IOverflowWarning) except NameError: pass # OverflowWarning was removed in

Re: [Zope-dev] Zope 2.12.0 released

2009-10-05 Thread Dragos Chirila
I took the steps: - installed Python 2.6.2 - downloaded Zope2-2.12.0-py2.6-win32.egg - ..\Scripts\easy_install.exe Zope2-2.12.0-py2.6-win32.egg - create a zope instance with ..\Scripts\mkzopeinstance.exe Is this the correct way, right? On Mon, Oct 5, 2009 at 12:35 PM, Chris Withers

Re: [Zope-dev] Zope 2.12.0 released

2009-10-05 Thread Chris Withers
Dragos Chirila wrote: I took the steps: - installed Python 2.6.2 - downloaded Zope2-2.12.0-py2.6-win32.egg - ..\Scripts\easy_install.exe Zope2-2.12.0-py2.6-win32.egg - create a zope instance with ..\Scripts\mkzopeinstance.exe Try the virtualenv option here:

Re: [Zope-dev] zope.filerepresentation release

2009-10-05 Thread Hanno Schlichting
Hi. On Mon, Oct 5, 2009 at 12:13 PM, Martin Aspeli optilude+li...@gmail.com wrote: I'd very much like a release of this. :) Would anyone mind making a 3.5.1 release, or else give me PyPI rights so that I can do it myself. I gave you owner rights for this package. Hanno

Re: [Zope-dev] zope.filerepresentation release

2009-10-05 Thread Fabio Tranchitella
Hello, * 2009-10-05 12:15, Martin Aspeli wrote: Would anyone mind making a 3.5.1 release, or else give me PyPI rights so that I can do it myself. Shouldn't this be 3.6.0? Best regards, Fabio ___ Zope-Dev maillist - Zope-Dev@zope.org

Re: [Zope-dev] zope.filerepresentation release

2009-10-05 Thread Martin Aspeli
Fabio Tranchitella wrote: Hello, * 2009-10-05 12:15, Martin Aspeli wrote: Would anyone mind making a 3.5.1 release, or else give me PyPI rights so that I can do it myself. Shouldn't this be 3.6.0? I don't care one way or the other. 3.6.0 is fine by me. Martin -- Author of

Re: [Zope-dev] zope.filerepresentation release

2009-10-05 Thread Hanno Schlichting
On Mon, Oct 5, 2009 at 1:18 PM, Martin Aspeli optilude+li...@gmail.com wrote: Fabio Tranchitella wrote: * 2009-10-05 12:15, Martin Aspeli wrote: Would anyone mind making a 3.5.1 release, or else give me PyPI rights so that I can do it myself. Shouldn't this be 3.6.0? I don't care one way

[Zope-dev] Zope Tests: 8 OK

2009-10-05 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list. Period Sun Oct 4 12:00:00 2009 UTC to Mon Oct 5 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun Oct 4 20:50:56 EDT 2009 URL:

Re: [Zope-dev] Updating the ZTK KGS

2009-10-05 Thread Martijn Faassen
Thomas Lotze wrote: Having worked on and released new versions of a few ZTK packages recently, I'm tempted to update the ZTK KGS (ztk.cfg) accordingly now. However, as there doesn't seem to be an agreed process about this and in an attempt not to step on anyone's toes, I'd like to ask first

Re: [Zope-dev] Zope 2.12.0 released

2009-10-05 Thread Dragos Chirila
Chris, You were right; I tried on a fresh Python 2.6.3 installation and it worked - Zope instance started without errors. Dragos On Mon, Oct 5, 2009 at 12:43 PM, Chris Withers ch...@simplistix.co.uk wrote: Dragos Chirila wrote: I took the steps: - installed Python 2.6.2 - downloaded

Re: [Zope-dev] Updating the ZTK KGS

2009-10-05 Thread Thomas Lotze
Martijn Faassen wrote: So I'd propose the following development process: * developers can change the version numbers in the ZTK * if the compattests all run, they can check in I'll go ahead and update the KGS with my proposed new versions then; if someone experiences a problem with this,

Re: [Zope-dev] Updating the ZTK KGS

2009-10-05 Thread Hanno Schlichting
On Mon, Oct 5, 2009 at 4:44 PM, Thomas Lotze t...@gocept.com wrote: I see two options: - make ztk.cfg available from zope.org (why docs.zope.org, btw?) under a  versioned URL - release a ztk egg that depends on the exactly versioned packages The latter is probably the more reusable. I'd

[Zope-dev] Zope 2 WebDAV and acquisition

2009-10-05 Thread Martin Aspeli
Hi, In my travails through the ZPublisher and WebDAV, I've come up with another fun thing. As far as I can tell, traversal via acquisition doesn't make any sense for a WebDAV request. If I have /foo and /bar, but not /bar/foo, then traversal to /bar/foo over WebDAV should not acquire /foo and

Re: [Zope-dev] Zope 2 WebDAV and acquisition

2009-10-05 Thread Martin Aspeli
Martin Aspeli wrote: Hi, In my travails through the ZPublisher and WebDAV, I've come up with another fun thing. As far as I can tell, traversal via acquisition doesn't make any sense for a WebDAV request. If I have /foo and /bar, but not /bar/foo, then traversal to /bar/foo over

Re: [Zope-dev] Zope 2 WebDAV and acquisition

2009-10-05 Thread Martin Aspeli
Martin Aspeli wrote: Martin Aspeli wrote: Martin Aspeli wrote: Hi, In my travails through the ZPublisher and WebDAV, I've come up with another fun thing. As far as I can tell, traversal via acquisition doesn't make any sense for a WebDAV request. If I have /foo and /bar, but not

Re: [Zope-dev] Zope 2.12: mkzopeinstance, runzope and zopectl - a small proposal

2009-10-05 Thread Chris Withers
(updating myself much much later) Chris Withers wrote: yuppie wrote: You ripped my sentence out of context. We were talking about Zope 2.12. And Zope 2.12 currently doesn't use buildout for setting up instances. Sure it does. I've published the recipe. There's no more needed than that...

Re: [Zope-dev] Zope 2 WebDAV and acquisition

2009-10-05 Thread Shane Hathaway
Martin Aspeli wrote: Can anyone explain why that condition is there? Otherwise, I'll rip it out. ;-) As I recall, this code is convoluted because it's hard to tell whether an HTTP request is a WebDAV request. If there is now a way to clearly distinguish WebDAV requests, then I imagine this

Re: [Zope-dev] Zope 2 WebDAV and acquisition

2009-10-05 Thread Martin Aspeli
Shane Hathaway shane at hathawaymix.org writes: Martin Aspeli wrote: Can anyone explain why that condition is there? Otherwise, I'll rip it out. As I recall, this code is convoluted because it's hard to tell whether an HTTP request is a WebDAV request. If there is now a way to