Eron,
I have not installed the beta4 binary, so I havent seen what you're
seeing. I sort of lack the cycles to do anything about this at the
moment, but I'm sure everbody would be really pleased to hear what you
come up with.
- C
Eron Lloyd wrote:
> Chris (or anybody else),
>
> Have you
Chris (or anybody else),
Have you tried to install Beta4 using the linux binary package yet? I'm
trying to write a patch against it but the installation does in fact bomb out
each time I try to run it, even freshly untarred. The source TGZ works fine
and dandy, however. It seems compilezpy.py
I quite often use URLs that end in a slash (in fact, I prefer it that way,
since I then can add methods easily without having to care about if the url
is the root '/' or another object). This got me into trouble, though, since
unrestrictedtraverse can't handle URLs that end in a slash.
I have pat
Since Zope 2.4 and/or Python 2.1. (there are bugs in both that cause
crashes)
- Original Message -
From: "Rodrigo Leme de Mello" <[EMAIL PROTECTED]>
To: "Chris McDonough" <[EMAIL PROTECTED]>
Sent: Thursday, January 17, 2002 10:06 AM
Subject: Re: [Zope-dev] Zope is dying - Please, help!
> Just a quick note on this point, there are two points during startup when
a
> product can get control:
> 1) When the __init__.py is imported
> 2) When the initialize function within that __init__.py is called.
I think Godefroid's case it would definitely want to be in __init__.py
*outside* of t
Just a quick note on this point, there are two points during startup when a
product can get control:
1) When the __init__.py is imported
2) When the initialize function within that __init__.py is called.
These seem to occur quite far apart in terms of loaded modules so to get
something done early
The "compiler" module that ships with 2.4.3 "RestrictedPython" still has a
few bugs in it that could cause this behavior. 2.4.4 will be a bugfix
release to solve this.
Please either wait for 2.4.4 or use 2.5beta4.
- c
- Original Message -
From: "Rodrigo Leme de Mello" <[EMAIL PROTECTED
Please read both the Zope developer's guide and the document UNITTEST.txt in
the Zope doc directory. These pages are also helpful:
http://dev.zope.org/CVS/ZopeTestingGuidelines ,
http://diveintopython.org/roman_divein.html ,
http://pyunit.sourceforge.net/pyunit.html .
- C
- Original Message
Hi all,
I am using python 2.1.2 with zope 2.4.3, i've compiled python --without-py_malloc and
also tried othe combinations as 2.1.1 with
2.4.2; 2.1.1 with 2.4.3 and still getting the same error.
I'm not using pcgi, only zserver and apache with proxy pass.
I do need to solve this. Does anybody
I have had a lot of interest in a couple of my products, and I would like to
ensure they are as stable as I can make them. I have heard a lot on here
about unit-testing, is there a guide to creating unit-tests? Is there a
procedure, or something to follow so that I can be sure I am testing "the
ri
> I do not know what you mean by a 'monkeypatch' but it is certainly worth
> it to add the patch to 2.3.x and 2.4.x branches.
Thanks very much for the patch! We don't maintain 2.3.X anymore (at
least not that I know of, although somebody probably should). And the
2.4 branch is a little up in
At 18:43 16/01/2002, you wrote:
Sorry about cross-posting but I think the following info is worth reading
for both zope-users and developers.
>Note that up until Zope 2.5.0b4 there is a bug in the way module security
>assertions are handled that makes it impossible to declare more than one
>
Chris Withers wrote:
> Shame though, since storing objects in the session so different frames can get
> hold of them without lots of computation seemed like a realyl ncie idea :-S
Maybe you can use a RAM cache manager for this? It doesn't store stuff
in ZODB.
>>the "main" storage in the sessio
A while back, someone was able to provide an Python Script that *always*
crashed Zope.That's how Evan was able to determine that there was a
stack size computation bug in the compiler module. I *think* he may
have turned it in to a unit test.
The current Zope test suite is the first line
Hi Tony,
The combination of Zope 2.4.4 and Python 2.1.2 will be the "right"
combination. If you can't wait for Zope 2.4, you can use Zope 2.5
(which I believe already has the requisite fixes), although of course
it's still in beta.
I think you'll need to recompile your extensions -- I'm not
From: "Chris McDonough" <[EMAIL PROTECTED]>
> Leonardo Rochael Almeida wrote:
>
> > Also, what about the --pymalloc? Is the binary Zope Python going to be
> > compiled with it? should I still fear it?
>
> Dunno. Was it compiled in before? Isn't this an issue that is solved
> in a roundabout way
Chris McDonough wrote:
>
> I think the answer here might be "don't do that" ;-).
Yeah, that's what we thought ;-)
Shame though, since storing objects in the session so different frames can get
hold of them without lots of computation seemed like a realyl ncie idea :-S
> the "main" storage in
Hi all,
I want to upgrade to python 2.1.2 (from an existing 2.1 installation) and at
the same time upgrade to 2.5b4 in the hopes that this combination will fix
the threading problem under Solaris.
Q1: Is this the right combination to use, I've read that I should use 2.1.2
and 2.4.4 (possible numb
18 matches
Mail list logo
