Alexander Limi schrieb:
On Fri, 18 Nov 2005 06:56:32 -0800, Andreas Jung
[EMAIL PROTECTED] wrote:
In general such changes should be made on the HEAD (for next 2.10
release).
OK. I was aiming for a quick sprint to get some small changes into 2.9
before release (ie. no actual code
--On 22. November 2005 09:11:13 +0100 Tino Wildenhain [EMAIL PROTECTED]
wrote:
Alexander Limi schrieb:
On Fri, 18 Nov 2005 06:56:32 -0800, Andreas Jung
[EMAIL PROTECTED] wrote:
In general such changes should be made on the HEAD (for next 2.10
release).
OK. I was aiming for a quick
Andreas Jung schrieb:
--On 22. November 2005 09:11:13 +0100 Tino Wildenhain
[EMAIL PROTECTED] wrote:
Alexander Limi schrieb:
On Fri, 18 Nov 2005 06:56:32 -0800, Andreas Jung
[EMAIL PROTECTED] wrote:
In general such changes should be made on the HEAD (for next 2.10
release).
OK. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
FWIW:
Alot. :)
$ pwd
/home/tseaver/projects/Zope-CVS/Zope-2_8-branch
$ find . -name *.py | grep -v build-base | xargs grep -l whrandom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Fri, 2005-11-18 at 08:43 -0500, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Paul Winkler wrote:
On Thu, Nov 17, 2005 at 02:33:10PM -0200, Sidnei da Silva wrote:
I might have asked
I'd like to upgrade
bug 1950 to critical.
Is there an easy way
to do this?
___
Daniel PozmanterSiteworx,
Inc.
"Festina Lente" - Gaius
Julius
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
We don't have the collective time right now to market this, but it's
very cool so we thought someone might get some use out of it.
Brian Lloyd has developed zope.testrecorder, a cross-browser (IE,
Firefox, Safari) JavaScript app that records browser events (clicking,
entering text, etc.) and
Chris Withers wrote at 2005-11-21 16:33 +:
...
here's a line from one of our event logs:
2005-11-17T08:00:27 INFO(0) ZODB conflict error at /some_uri
(347 conflicts since startup at 2005-11-08T17:56:20)
What is this telling me?
It is incredibly stupid.
The message above only tells you,
Florent Guillaume wrote at 2005-11-22 00:13 +0100:
...
I'm actually not sure what's logged when a Conflict Error makes it back
to the users, offhand I don't see anything in my logs. Can someone
confirm or infirm that fact?
If nothing is logged, I'll add something at level ERROR.
I fear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Pozmanter wrote:
I'd like to upgrade bug 1950 to critical.
Is there an easy way to do this?
I just followed up to the bug report: we need a test case, written in
Python, which demonstrates the leak.
The usual course when trying to isolate
Cool, thanks!
Jim
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
FWIW:
Alot. :)
$ pwd
/home/tseaver/projects/Zope-CVS/Zope-2_8-branch
$ find . -name *.py | grep -v build-base | xargs grep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Pozmanter wrote:
Yes, I saw the follow up.
So is there no way to change the severity of a bug?
It could be changed, but you need to persuade us that it is a
showstopper first. Labeling the bug critical is a claim that we
have to fix it
Dan Pozmanter wrote:
Sure thing:
I was mucking around in _Acquisition.c with getattr, findattr, etc,
and I noticed checked to see if my code was leaky.
It was! I then checked just vanilla code, and found the same
leak (only much much smaller).
So here is what I did to make things more
Isn't a try: ... finally: ... needed here?
Florent
Tres Seaver wrote:
Log message for revision 40329:
Suppress expected DeprecationWarning output in test.
Changed:
U Zope/trunk/lib/python/Products/PythonScripts/tests/testPythonScript.py
-=-
Modified:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
Isn't a try: ... finally: ... needed here?
Yup. Or else call '_free_warning_output' call in 'tearDown' (which I
jsut checked in). Thanks for the catch!
Tres.
- --
On Mon, 21 Nov 2005 06:47:34 -0800, Chris Withers [EMAIL PROTECTED]
wrote:
Jens Vagelpohl wrote:
IMHO if this is just UI changes that improve usability it should be
OK to flout the rules a bit. The rules are there to ensure code
quality and stability in a release branch - I doubt small
16 matches
Mail list logo
