Hello zope-dev!
I have a question about PropertyManager._setPropValue in 2.6 and its changed
version in 2.7-2.8.
I found this revision
http://svn.zope.org/Zope/trunk/lib/python/OFS/PropertyManager.py?rev=24349view=rev
Why in this method added conversion to the tuple for all the
Victor Safronovich wrote:
I have a question about PropertyManager._setPropValue in 2.6 and its changed
version in 2.7-2.8.
I found this revision
http://svn.zope.org/Zope/trunk/lib/python/OFS/PropertyManager.py?rev=24349view=rev
Why in this method added conversion to the tuple
Hi,
because of the fact that we are switching to a time-based release cycle for
Zope 2 and Zope 3. I would like to discuss how deal with the maintenance of
older branches. My idea is to support branches for one year from now on.
Zope 2.7 should be maintained until the end of this year, Zope
Hi everyone,
with Zope 2.9 and Zope 3.2 we are switching to a time-based release cycle.
Major release are supposed to appear every six months (December and June).
For Zope 2.9 the schedule is as follows:
- 2.9 beta 1 on 2005-11-07
- 2.9 beta 2 aka RC1 on 2005-11-20
- 2.9 final on 2005-12-01
Ahoy,
I was
poking around in _Acquisition.c, and noticed my memory usage
spiked.
Returning to the
vanilla code (2.8.2-final), I noticed the same spike (just less
pronounced).
(If you refresh the
page a few gazillion times this pops up).
I would not
categorize this as an actual bug
Andreas Jung wrote:
What do you think?
Sounds good to me :-)
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist - Zope-Dev@zope.org
Nobody has yet reported a memory leak symptom against any particular
piece of Zope 2.8.X yet, AFAIK.
On Oct 31, 2005, at 6:34 PM, Dan Pozmanter wrote:
Ahoy,
I was poking around in _Acquisition.c, and noticed my memory
usage spiked.
Returning to the vanilla code (2.8.2-final), I noticed
