Hello,
I have been using the Structured Document (SD) product with page
templates (to provide some content sections that a client can edit
using structured text).
Now I would like to use ReStructuredText Document (RSTD) instead of SD.
I have been using code like this in a page template to render
Thanks for that. It worked perfectly.
Out of interest, why am I unable to access the method from with my Zope
python code? What is a private object, and why is it private?
Thanks,
Nick
Martijn Pieters wrote:
On 2/19/06, Nicholas Watmough <[EMAIL PROTECTED]> wrote:
I tried using unrestri
On Thursday 23 February 2006 20:29, Jim Fulton wrote:
> This is quite a document and vision. I hope we can pull something
> like it off. (Like many, I recognize the daunting size of the task.)
I have already working parsers and writers for all file formats. I have also a
preliminary (but tested
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
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).
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 (P
On Tue January 31 2006 07:47, Chris Withers wrote:
> > I do it though the webinterface with a wget from the crontab:
> Oh, ouch ouch bad fragile pain failure suffering...
>
> URL whacking is evil and must be punished...
How is this different than clicking on the Pack button in the ZMI? What's
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.
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
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 intern
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
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
On Thu, Feb 23, 2006 at 11:27:59AM -0500, Derrick Hudson wrote:
> Does 'zopectl run' require exclusive access to the database? (IOW
> must the zope server be stopped before zopectl run can be used?)
Yes, IFF you are not running zeo.
That's another useful reason to use zeo :-)
> I just came acr
Chris,
On Tue, Jan 31, 2006 at 01:36:36PM +, Chris Withers wrote:
| ZEO & Stepper
Is ZEO required to use Stepper?
| Or if you don't like Stepper, then zopectl run...
Does 'zopectl run' require exclusive access to the database? (IOW
must the zope server be stopped before zopectl run can
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 re
Title: RESOLUTION: Can Zope 2.9 Coexist With Zope 2.6 Using Different Ports?
Thanks for the help everyone. I needed to make the $Instance/var and $Instance/log directories readable and writable to the user that Zope 2.9 ran as. Once I did that the problem went away.
On 2/23/06, Brian Sullivan <[EMAIL PROTECTED]> wrote:
> I was assuming that it would somehow be easy to do the equivalent to
> Javascript "escape/unescape" functions in a Python script but for some
> reason I just can't find out how to do it.
from Products.PythonScripts.standard import url_quote,
>
> >I was assuming that it would somehow be easy to do the equivalent to
> > Javascript "escape/unescape" functions in a Python script but for some
> > reason I just can't find out how to do it.
> >
> > Maybe I can't see the forest for the trees. Anybody out there have a
> > cluestick to whack me
- Original Message -
From: "Brian Sullivan" <[EMAIL PROTECTED]>
To: "zope list user"
Sent: Thursday, February 23, 2006 10:45 AM
Subject: [Zope] Python equivalent to Javascript "escape/unescape"
I was assuming that it would somehow be easy to do the equivalent to
Javascript "escape/une
I was assuming that it would somehow be easy to do the equivalent to
Javascript "escape/unescape" functions in a Python script but for some
reason I just can't find out how to do it.
Maybe I can't see the forest for the trees. Anybody out there have a
cluestick to whack me with?
__
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. Ev
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 promp
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 t
I'm running Zope 2.8.1-final, python 2.3.5, linux2 and Zope 2.6.1 python
2.1.3, linux2 on the same server so I don't see why you cant' also run Zope
2.9. More than likely each of your configurations have the same path to the
lock file. Edit zopefolder/etc/zope.conf where zopefolder is the nam
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 th
Chris Withers napisał(a):
Pawel Lewicki wrote:
Any clues?
Products used:
- ExternalFile 1.2.0
- CMFExternalFile 0.5
- Plone 2.0.5
None of these are products I'd trust. Use a ZODB analysis tool to find
out the types of objects you have in your database and see which product
is causing the iss
Chris Withers wrote:
Nicolas Georgakopoulos wrote:
I don't have any experience writing external products... should be
easy if I finish the python programming part as a simple traditional
python release and then to implement it as a Zope product ?
Yeah, sure be easy enough... and we're to
J Cameron Cooper wrote:
I don't know if this is your problem, but you can't run two instances off
the same ZODB unless you use ZEO.
And it's certainly an extremely bad idea to try and do so with two
different versions of Zope, whatever your setup!
how you've installed things.) But it's cert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
you may face several problems with shared hosts:
- - you may not have the privilege to configure apache to your needs (you
may be able to via .htaccess)
- - you may lack the privilege to compile/install software (including the
Zope instance. Rem
28 matches
Mail list logo