[Zope3-Users] Re: browser:form
Jeff Shell wrote: On 2/21/06, David Johnson [EMAIL PROTECTED] wrote: With formlib, you'd be able to get/set this in the update() method, or if you're clever, you can do it in publishTraverse so you can have url like '.../mycontacts/contact/1234'. Thanks for the mini-tutorial :) Will publishTraverse work with Five? -- Suresh ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] zope3 debian/testing ZopeXMLConfigurationError
Martin Künstner wrote: hello list, I'm new to zope3 and want to install it on a debian/testing box. when i want to start the sandbox instanz with the following command mawensi:/home/martin# /var/lib/zope3/instance/sandbox/bin/runzope i get this error mesage: [...] I've tried to upgrade twisted but I think i have all the required packages installed. what went wrong ? You should probably report this to the Debian Zope packaging team. S. -- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps Gestion de contenu web / portail collaboratif / groupware / open source! ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] The Zope Software Certification Program and CommonRepository Proposal
On 2/22/06, Lukasz Lakomy [EMAIL PROTECTED] wrote: Hello Stephan and all 1. Zope Certified Company. Soemthing similar to certificates given by commercial companies: Microsoft, Oracle etc. Sometimes there are companies creating comemrcial aplications with Zope. They have no possibility to make them open source or to contribute to Zope 3 development. But they want to measure their quality of work and comapre to other companies/competitors. So I'm thinking also about levels of maturity for company. It could be achieved by participations in some trainings or maybe by audits from Zope Corporation. It won't be free of course! It always look nice on the comapny website where there is a logo Technology X certifies and makes the comapny trustworthy. 2. Zope Certified Programmer. They are also certificates for persons who know given technology. Why we cannot make it for Zope also? For example if a company wats to employ a programer it could state that he needs Zope Certified Programmer Level X. This shows the maturity of developer and be motivating for him. The base leves should be obtained by sending some piece of code, next level after some Internet chat, rest maybe on exams during sprints or in the company that are being certified. The knowledge for base levels should be checked via Internet because of long distances. It also should be free or very cheap, the higher levels may be more expensive. Doing these things requires that you make a complete certification scheme, with several courses and tests to make sure that it people have thr right knowledge, and update courses and update tests for new versions, and handling of the database of certified people and companies and making sure it's up to date and all that. All in all there would have to be several full time people involved in this. So, it's quite evident that this is nothing the community has any sort of capacity to handle. There are however, companies that do this. But as far as I know, they do it because another company pays them. Developing the courses and the tests is a heavy investment, that has to be slowly recouperated over time by certifying people, and certification companies would probably not want to take that risk with a small market such as Zope development. That would men that the Zope foundation would have to pay for it, and I don't think it can afford to, and even if it could, there are better ways. However, the Zope Foundation provides an alternative. Organisations and people can become members of the foundation. I don't remember the details, you'd have to check out that discussion instead. Although it's not certification, it provides people and companies with some sort of stamp of we are commited and knowledgable in this area which of course is the whole point of certification. :) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Debugging doctests
On 2/21/06, Stephan Richter [EMAIL PROTECTED] wrote: On Tuesday 21 February 2006 12:14, Lennart Regebro wrote: (btw, through all this, I assume that Jims fix for the doctest debugging problem that he mentioned did work, and that you now can insert an import pdb;pdb.set_trace() in the middle of the doctests. Right?) This has been fixed since ages. :-) Ah, not in Zope 2.9 it seems. Is this expected, or an I doing something wrong? I'm running the Five tests with bin/zopectl test --dir Products/Five as usual, and having a set_trace() in the doctests behaves exactly as with the old test runner, where you have to debug though the doctest running as well, which makes it pretty useless... Hang on, I just tried it with Zope 3.2 too, and it didn't work either. What am I doing wrong? -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: [Zope] Debugging doctests
On Thursday 23 February 2006 06:53, Lennart Regebro wrote: Ah, not in Zope 2.9 it seems. Is this expected, or an I doing something wrong? I'm running the Five tests with bin/zopectl test --dir Products/Five as usual, and having a set_trace() in the doctests behaves exactly as with the old test runner, where you have to debug though the doctest running as well, which makes it pretty useless... How do you want to use the debugger? I run the tests, if the set_trace() occurs it throws me to the prompt and all is fine. I can use the debugger as usual. There used to be an issue with the debugger not displaying anything, since doctests mess with stdout and that has been fixed. This is what Benji and I were talking about. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: [Zope] Debugging doctests
On 2/23/06, Stephan Richter [EMAIL PROTECTED] wrote: How do you want to use the debugger? I'd like to be able to step through the tests. I run the tests, if the set_trace() occurs it throws me to the prompt and all is fine. I can use the debugger as usual. When I do this, I get a prompt. Pressing next returns to the running of the tests, not the next line of the test. Here is an example: import pdb;pdb.set_trace() gsm = zope.component.getGlobalSiteManager() gsm.provideUtility(I1, ob) gsm.provideUtility(I11, ob11) When I run this, my debuggning session looks like this: $ bin/zopetest --dir zope/component Running unit tests: --Return-- /opt/Zope-3.2.0/lib/python/zope/testing/doctest.py(351)set_trace()-None - pdb.Pdb.set_trace(self) (Pdb) s --Return-- doctest zope.component.tests.test_getAllUtilitiesRegisteredFor[4](1)?()-None - import pdb;pdb.set_trace() (Pdb) s /opt/Zope-3.2.0/lib/python/zope/testing/doctest.py(1257)__run() - self.debugger.set_continue() # Example Finished (Pdb) s --Call-- /opt/Zope-3.2.0/lib/python/zope/testing/doctest.py(353)set_continue() - def set_continue(self): (Pdb) s /opt/Zope-3.2.0/lib/python/zope/testing/doctest.py(356)set_continue() - if self.__debugger_used: (Pdb) s /opt/Zope-3.2.0/lib/python/zope/testing/doctest.py(357)set_continue() - pdb.Pdb.set_continue(self) (Pdb) s --Call-- /usr/lib/python2.4/bdb.py(196)set_continue() - def set_continue(self): (Pdb) s /usr/lib/python2.4/bdb.py(198)set_continue() - self.stopframe = self.botframe (Pdb) s As you see, I can't even step into that next line. And even if I could, the necessity of having to step through the doctestrunning would be a major pain in the ass. Here is a non-doctest exampe as comparison. This is what I want: import pdb;pdb.set_trace() sm = zapi.getSiteManager() sm.registerUtility(IDummyUtility, dummy1) sm.registerUtility(IDummyUtility, dummy2) - sm = zapi.getSiteManager() (Pdb) n /home/zopes/cps34/Products/Five/site/tests/test_utility.py(209)test_registeringTwiceIsConflict() - sm.registerUtility(IDummyUtility, dummy1) (Pdb) n /home/zopes/cps34/Products/Five/site/tests/test_utility.py(210)test_registeringTwiceIsConflict() - sm.registerUtility(IDummyUtility, dummy2) (Pdb) s --Call-- /home/zopes/cps34/Products/Five/site/localsite.py(147)registerUtility() - def registerUtility(self, interface, utility, name=''): (Pdb) I can't seem to be able to do this. There used to be an issue with the debugger not displaying anything, since doctests mess with stdout and that has been fixed. This is what Benji and I were talking about. Oh. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: [Zope] Debugging doctests
On Thursday 23 February 2006 08:13, Lennart Regebro wrote: As you see, I can't even step into that next line. And even if I could, the necessity of having to step through the doctestrunning would be a major pain in the ass. Ok, I have never needed this. And I can see why it does not work. Every doctest line is its own expression. I personally can live with that limitation. As I said, I have never needed this. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
Stephan Richter wrote: On Thursday 23 February 2006 08:13, Lennart Regebro wrote: As you see, I can't even step into that next line. And even if I could, the necessity of having to step through the doctestrunning would be a major pain in the ass. Ok, I have never needed this. And I can see why it does not work. Every doctest line is its own expression. I personally can live with that limitation. As I said, I have never needed this. On the rare occasions when I have wanted to do that, I just make whatever I want to step through into a single doctest line, like so: a = 1 b = 2 c = a + b Becomes if 1: ... import pdb;pdb.set_trace() ... a = 1 ... b = 2 ... c = a + b Ugly, but it works. I too would like it if a bare set_trace() would allow you to step through a doctest, but don't know if anyone is sufficiently motivated to figure out the details (or a suitable alternative). -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
On Feb 23, 2006, at 10:10 AM, Benji York wrote: [...] if 1: ... import pdb;pdb.set_trace() ... a = 1 ... b = 2 ... c = a + b Oh yeah. I've had to do stuff like that too. :-) ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
I dunno about sucking because they are quite good for documentation, but I tend to write plain-old unittests instead of doctests when I'm testing without any pretense towards writing documentation. If you test internals of a class in a doctest, the doctest body gets pretty cluttered, which tends to defeat the documentation-esque-ness of them. Being able to set a breakpoint in the test body is important for me too. I probably could be setting breakpoints once I'm in the debugger, but it's often easier to just stuff in a pdb.set_trace() before the line of code that I want to examine. And putting a set trace in a unittest is a natural thing to do, because you know the set trace will only get invoked once during a test run (as opposed to putting it right in the app code, where it might get invoked by accident through a different test). Setting breakpoints in unittest- tests is typically more fruitful than putting them in doctest-tests for the reasons that have been talked about in this thread. - C On Feb 23, 2006, at 11:27 AM, Lennart Regebro wrote: On 2/23/06, Gary Poster [EMAIL PROTECTED] wrote: You effectively can't step through all the tests (with a single pdb). You can step through a single line in the test well. While it sounds limiting, that has proved quite sufficient for me in practice. YMMV, of course. Sigh. doctests really do suck. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: browser:form
On 2/22/06, suresh [EMAIL PROTECTED] wrote: Jeff Shell wrote: On 2/21/06, David Johnson [EMAIL PROTECTED] wrote: With formlib, you'd be able to get/set this in the update() method, or if you're clever, you can do it in publishTraverse so you can have url like '.../mycontacts/contact/1234'. Thanks for the mini-tutorial :) Will publishTraverse work with Five? I'm not sure. I haven't used Five. But if it doesn't, you *should* be able to get by with ``__bobo_traverse__``. I think the signature is the same - accepts a request and a name, and should return a callable or traversable object:: def __bobo_traverse__(self, REQUEST, key): self.contactid = key return self *Should* work if publishTraverse doesn't. But since publishTraverse is a core protocol from zope.publisher, I would expect Five views to support it. -- Jeff Shell ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
Chris McDonough wrote: I dunno about sucking because they are quite good for documentation, but I tend to write plain-old unittests instead of doctests when I'm testing without any pretense towards writing documentation. If you test internals of a class in a doctest, the doctest body gets pretty cluttered, which tends to defeat the documentation-esque-ness of them. Are you talking about doctests in docstrings? If so, I definitely see downsides to that use case. I was talking about doctests in stand-alone text files. That's my (and several others) preferred way of using them. If you /were/ talking about stand-alone doctests, then I have no idea what you're talking about. :) -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
On 2/23/06, Chris McDonough [EMAIL PROTECTED] wrote: I dunno about sucking because they are quite good for documentation, Oh, absolutely. but I tend to write plain-old unittests instead of doctests when I'm testing without any pretense towards writing documentation. Exactly my sentiments. Being able to set a breakpoint in the test body is important for me too. I probably could be setting breakpoints once I'm in the debugger Well, how do you set a breakpoint in something which has no py-file and line, but is in a text-document or string? :-) Not to mention, doctests are not debuggable from WingIDE. ;-) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
On Feb 23, 2006, at 1:17 PM, Benji York wrote: Chris McDonough wrote: I dunno about sucking because they are quite good for documentation, but I tend to write plain-old unittests instead of doctests when I'm testing without any pretense towards writing documentation. If you test internals of a class in a doctest, the doctest body gets pretty cluttered, which tends to defeat the documentation-esque-ness of them. Are you talking about doctests in docstrings? If so, I definitely see downsides to that use case. I was talking about doctests in stand-alone text files. That's my (and several others) preferred way of using them. Either. If you /were/ talking about stand-alone doctests, then I have no idea what you're talking about. :) It's just opinion, but for example, I don't think zope/wfmc/xpdl.txt reads much better as a doctest than it would as a plain old unittest. But it's of course a judgment call. - C ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
Chris McDonough wrote: On Feb 23, 2006, at 1:17 PM, Benji York wrote: If you /were/ talking about stand-alone doctests, then I have no idea what you're talking about. :) It's just opinion, but for example, I don't think zope/wfmc/xpdl.txt reads much better as a doctest than it would as a plain old unittest. I agree that xpdl.txt is only marginally better as a doctest in its current form. I'd also claim that it's nearly a degenerate doctest. It really needs more text. But it's of course a judgment call. Perhaps this is just one of those to-each-his-own things. shrug My own are doctests. ;) -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
On Feb 23, 2006, at 1:57 PM, Benji York wrote: But it's of course a judgment call. Perhaps this is just one of those to-each-his-own things. shrug My own are doctests. ;) Sure. I actually really appreciate reading good doctests, they help a lot, and they beat not having any docs at all any day! A non-sequitur: For truly standalone packages, I suspect that people expect some form of non-executable narrative documentation to be included that ties the continued use of the package together with its implementation. In my experience, it's easy to get lured into thinking that you've documented a package properly because it has doctests and interface documentation, when in reality it probably needs some other form of documentation beyond the doctests (e.g. high- level overview of purpose, how to install it, what other packages it depends upon, which versions of Python/Zope it works with, who is responsible for maintaining the package, where to report bugs, and so on). I suppose this is really a packaging issue, but it would be nice if more packages in the zope namespace package were treated as islands like this that could be installed separately from Zope proper. It would also likely help prevent inappropriate dependencies from creeping in. Zope 2 wasn't born a mess of spaghetti dependencies, they just sort of grew like weeds over time. - C ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
On Thursday 23 February 2006 13:37, Lennart Regebro wrote: Not to mention, doctests are not debuggable from WingIDE. Maybe we should have a WingIDE sprint in Boston at some point. This would be a good topic. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
On Thursday 23 February 2006 14:16, Chris McDonough wrote: (e.g. high- level overview of purpose, how to install it, what other packages it depends upon, which versions of Python/Zope it works with, who is responsible for maintaining the package, where to report bugs, and so on). I suppose this is really a packaging issue, but it would be nice if more packages in the zope namespace package were treated as islands like this that could be installed separately from Zope proper. The ZSCP tries to exactly capture this information and provide it via its site. So, I take it that you are a second voter in favor of not requiring all tests to be doctests. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: [Zope] Debugging doctests
On Feb 23, 2006, at 4:51 PM, Stephan Richter wrote: So, I take it that you are a second voter in favor of not requiring all tests to be doctests. If the ZSCP thing takes off, I think test/doc req'ts should be somewhat looser than mandating a particular test/doc framework (something along the lines of must have good test coverage and appropriate narrative documentation, maybe with examples of what this means that could be in doctest format by default). Would that be acceptable? - C ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Cometh the hour... ZCML Configurator
Wanna watch a 700Kb screencast showing the pre-alpha ZCML Configurator? http://www.peterbe.com/zope/zcmlconfigurator/ It's not finished yet. I've only spent a day and a half on it and it's missing some important Save features still. It's a commandline tool that fires up a browser (notice the -b on the command line in the beginning) to allow you to manipulate a configure.zcml file as a DOM tree with lots of nifty javascript fluff and AJAX. I've tested it with Firefox (linux, windows) and I'm not going to lose any sleep over it not working in IE or Lynx. The only zope3 thing about this is that it can suggest clever new directives and default attributes when you add a new directive through the little wizard. There are still a few features missing and a few bugs that I need to iron out before I can launch anything, but I'm so excited about the quick progress that I thought I'd share it with you guys. The motivation was that I got annoyed by people complaining that XML is so bad. I like XML situps! (that, and that I wanted some excuse to dabble with more hardcore dom scripting) -- Peter Bengtsson, work www.fry-it.com home www.peterbe.com hobby www.issuetrackerproduct.com ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
RE: [Zope3-Users] Cometh the hour... ZCML Configurator
Hi Peter -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Bengtsson Sent: Friday, February 24, 2006 1:34 AM To: zope3-users@zope.org Subject: [Zope3-Users] Cometh the hour... ZCML Configurator Wanna watch a 700Kb screencast showing the pre-alpha ZCML Configurator? http://www.peterbe.com/zope/zcmlconfigurator/ It's not finished yet. I've only spent a day and a half on it and it's missing some important Save features still. It's a commandline tool that fires up a browser (notice the -b on the command line in the beginning) to allow you to manipulate a configure.zcml file as a DOM tree with lots of nifty javascript fluff and AJAX. I've tested it with Firefox (linux, windows) and I'm not going to lose any sleep over it not working in IE or Lynx. The only zope3 thing about this is that it can suggest clever new directives and default attributes when you add a new directive through the little wizard. There are still a few features missing and a few bugs that I need to iron out before I can launch anything, but I'm so excited about the quick progress that I thought I'd share it with you guys. The motivation was that I got annoyed by people complaining that XML is so bad. I like XML situps! (that, and that I wanted some excuse to dabble with more hardcore dom scripting) It's amazing, I'm looking forward to meet you at the Swiss Easter Sprint. Regards Roger Ineichen Projekt01 GmbH www.projekt01.ch _ END OF MESSAGE -- Peter Bengtsson, work www.fry-it.com home www.peterbe.com hobby www.issuetrackerproduct.com ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
