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
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
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
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
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
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.
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.
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
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
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,
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
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
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.
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
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
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
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
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
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
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
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
21 matches
Mail list logo
