[Zope-dev] removing test.py from path
Hello, Benji recently changed test.py in Z3 in order to avoid collision name with the standard python 'test' module. I bumped into the same problem running tests under Z 2.8. I would like to add this change as well in Z 2.8 bin/test.py if no one objects. Tarek -- Tarek Ziadé | Nuxeo R&D (Paris, France) CPS Plateform : http://www.cps-project.org mail: tziade at nuxeo.com | tel: +33 (0) 6 30 37 02 63 You need Zope 3 - http://www.z3lab.org/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] removing test.py from path
Tarek Ziadé wrote: Hello, Benji recently changed test.py in Z3 in order to avoid collision name with the standard python 'test' module. I bumped into the same problem running tests under Z 2.8. I would like to add this change as well in Z 2.8 bin/test.py if no one objects. oups, tipo, (Z2 trunk, i mean) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.10: Wiki started
Andreas Jung wrote: > > I created a wiki for the 2.10 development: > > <http://www.zope.org/DevHome/Projects/Wikis/DevSite/Projects/Zope2.10/FrontPage> > > > Feel free to contribute and comment. I've bumped into a problem in one of my five product lately, moving from 2.8 to 2.9 some Z3 package have disapeared to keep essential ones. This is pretty cool but hard to follow for developers. I'd like to suggest a page in this wiki to list included Z3 packages. This will be helpfull for developers that tries to integrate Z3 flavored code as much as possible in their Z2/Five products. Another page could list Z3 package people would like to see integrated in 2.10 (with some kind of proposal process maybe) (for example in my case i'd like to propose zope.app.cache as I use it in some five products, this is a small thing, but this is one more piece of logic/code I won't have to refactor :) ) Tarek -- Tarek Ziadé | Nuxeo R&D (Paris, France) CPS Plateform : http://www.cps-project.org mail: tziade at nuxeo.com | tel: +33 (0) 6 30 37 02 63 You need Zope 3 - http://www.z3lab.org/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Z2 / Z3 publisher
Hello, I've hurd a bit ago that some people wanted to replace Zope 2 publisher with Zope 3 one. Is it still planned ? Regards, Tarek ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Z2 / Z3 publisher
Sidnei da Silva wrote: >On Mon, Feb 13, 2006 at 12:44:44AM +0100, Tarek Ziadé wrote: >| Hello, >| >| I've hurd a bit ago that some people wanted to replace Zope 2 publisher >| with Zope 3 one. >| Is it still planned ? > >I've looked at it and opened a can of worms *wink*. OTOH, I've >factored out parts of Zope 2 ZPublisher enough to implement >IPublication. The next step from there is providing a compatible >request and response objects. > >This branch has a couple hacks to start up twisted and adapt the Zope >3 request/response to the expected Zope 2 ones. It does enough to >render the quickstart page with Zope 3's-included twisted and the >IPublication from Zope 2 but not much else. > >http://svn.zope.org/Zope/branches/publication-refactor/ > >I think the refactoring into IPublication can be merged to trunk >without problem, but the branch needs some cleaning before that. > > > neat ! ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] nt_svcutils
Hello, Is the small 'nt_svcutils' package has been eggified or is available somewhere as an egg ? I'd like to use it in a buildout recipe. I could copy the service.py but.. Thanks Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] PluggableAuthService and PrincipalDeleted
Hi, the IPrincipalDeleted event is never notified. As a matter of fact, this would be useful to be able to trigger some cleanup in various plugins, when user data has to be cleaned up. (FYI the PrincipalCreated event has a nice high level API _doAddUser that triggers IPrincipalCreated but no high level API for deletion) PAS also provides an IUserAdderPlugin interface for plugins that adds users. For deletion, I would like to do some changes into PAS: - add a IUserRemoverPlugin interface that adds a removeUser *or* rename IUserAdderPlugin to IUserManagerPlugin, but the latter would involve a lot of trouble i think - make ZODBUserManager implements it - add a notify(PrincipalDeleted(user_id)) in ZODBUserManager This would be helpfull to catch the event in various plugins My final goal is to make sure user properties are cleaned up in PlonePAS when a user is removed. Opinions ? Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.testing console script
Hi, I am comparing nose, py.test and zope.testing, and I realized zope.testing does not install a console script at Python level. it is not really a problem when working with a buildout-centric approach (thanks to zc.recipe.testrunner), but how can zope.testing be used with plain Python package ? Is there any installer available, that would allow running zope.testing from the shell ? To advocate zope.testing, I need to be able to demonstrate it can be used like the other tools available out there :D If nothing exists, I would like to suggest adding a setuptools console entry point in zope.testing setup.py file, to get a python script in the $PYTHON/bin folder, exactly like what zc.recipe.testrunner does. It could be called "zope.testrunner" maybe ? (nose= nostests, py.test = py.test) Regards Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing console script
On Thu, May 15, 2008 at 2:10 PM, Christian Theune <[EMAIL PROTECTED]> wrote: > On Thu, May 15, 2008 at 01:43:05PM +0200, Wichert Akkerman wrote: >> Previously Tarek Ziadé wrote: >> > I am comparing nose, py.test and zope.testing, and I realized >> > zope.testing does not install a console script at >> > Python level. >> > >> > it is not really a problem when working with a buildout-centric >> > approach (thanks to zc.recipe.testrunner), >> > but how can zope.testing be used with plain Python package ? >> > >> > Is there any installer available, that would allow running >> > zope.testing from the shell ? >> > >> > To advocate zope.testing, I need to be able to demonstrate it can be >> > used like the other tools available out there :D >> >> Is there a reason to advocate zope.testing over the others? Would it >> perhaps make more sense to use one of the more widely used tools instead >> of maintaing our own testing toolkit? Good question, I am not through in my comparison work, but the range of features are quite interesting in zope.testing ihmo, compared to others, and the zope community is used to it. > > For one: the others don't have layers. > Yes, and other provides test fixtures at method, class, module and (nose) package level. Although, py.test and nose provide a lighter approach where there's no need to use the unittest base classes, as the tools wraps on the fly any function, class so there's no need for extra boiler-plate code. py.test is using an iterator to launch tests immediatly while looking for them, the script is very fast This work i am doing is for a book, but I can publish the conclusion here if it can help making a decision on this. At this point I think that the work being done by Collin Winter in Python 3K will lead to a new testing framework in Python/unitest that will be less Java-oriented and lighter for test writer. >From there, the third party libraries will probably be reduced to the test discovery part. (I don't think this will be integrated in python but I might be wrong) My point of view is that zope.testing should evolve a little bit to be usable naturally from the command line like others, and maybe be more flexible in the discovering part, by wrapping tests that are not based on TestCase. This would make a unique testing tool, for the Zope community, and with a lighter way to write new tests, and with the command-line interface they are used to since years Tarek ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing console script
Phillip: > I suppose having it called 'test' (which is our convention) is a bit > arrogant. But calling it 'zope.testrunner' creates the allusion >that the > package is called zope.testrunner as well. How about 'run-zope.testing' or > something along those lines? Chris McDonough <[EMAIL PROTECTED]> wrote: > FWIW, we wrapped it up like this: > > http://svn.repoze.org/repoze.zope2/trunk/repoze/zope2/scripts/testrunner.py > > (that's the backend for a "zope2testrunner" console script) > mmm, what about a shorter name ? "ztests" Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing console script
On Fri, May 16, 2008 at 1:31 PM, Christian Theune <[EMAIL PROTECTED]> wrote: > On Thu, May 15, 2008 at 08:32:28AM -0400, Benji York wrote: > > On Thu, May 15, 2008 at 7:43 AM, Wichert Akkerman <[EMAIL PROTECTED]> > wrote: > > > Is there a reason to advocate zope.testing over the others? Would it > > > perhaps make more sense to use one of the more widely used tools > instead > > > of maintaing our own testing toolkit? > > > > I'd also like for us to adopt one of the more widely used test > > runners, but as mentioned in replies, there are some features in > > zope.testing that we depend on. If someone were adequately motivated > > and had sufficient time (neither of which I have, so I suspect no one > > else does either), it would be interesting to attempt to endue another > > test runner with the features we need (layers, etc.). > > I like our test runner and spent time refactoring it so we can actually > start > making changes again. I looked at other test runners (nose, py.test) and > didn't find anything compelling (to me) that we didn't already have. > > Christian > I am on Christian's side here: zope.testing is a great tool, used by many people, and with strong features, it looks like it does not need a lot of work to be usable without a buildout environment, and to have modern features nose and py.test provides. At least : 1. the console script (I'll add that in the trunk asap in any case) 2. being able to write tests without subclassing TestCase, in functions and classes (regexp based+ wrapping) 3. being able to create suites without any extra boiler-plate code, like nose does (afaik) Christian, are you willing to work on 2. and 3. ? ++ Tarek > > -- > Christian Theune · [EMAIL PROTECTED] > gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany > http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 > Zope and Plone consulting and development > -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Five, Z2 publisher, and zope.traversing views
Hi, When using a resource directory in a Zope 2 app, if the directory contains subdirectories that have the same names than the views defined in zope.traversing, this will lead to a bug when traversed because the Z2 Publisher will get slaped back. This can happen for example if your resourcedirectoy has a "lang" folder (or "vh" or "skin", etc..) We have wrote a small package with an adapter to make it work: http://ingeniweb.svn.sourceforge.net/svnroot/ingeniweb/iw.resourcetraverser/trunk/iw/resourcetraverser/README.txt But my understanding is that it would be better to fix it in Five, Opinions ? Regards, Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
