[Zope-dev] Re: [Zope-Checkins] CVS: Packages/ZODB - FileStorage.py:1.135.6.9
O... is this surfaced through the Zope undo tab?
Chris
Tim Peters wrote:
Update of /cvs-repository/Packages/ZODB
In directory cvs.zope.org:/tmp/cvs-serv29971/ZODB
Modified Files:
Tag: Zope-2_7-branch
FileStorage.py
Log Message:
UndoSearch._readnext(): Add the transaction size to the return value.
=== Packages/ZODB/FileStorage.py 1.135.6.8 = 1.135.6.9 ===
--- Packages/ZODB/FileStorage.py:1.135.6.8 Mon Feb 28 16:20:41 2005
+++ Packages/ZODB/FileStorage.pyTue Jun 14 16:46:32 2005
@@ -2374,6 +2374,7 @@
d = {'id': base64.encodestring(tid).rstrip(),
'time': TimeStamp(tid).timeTime(),
'user_name': u,
+ 'size': u64(tl),
'description': d}
d.update(e)
return d
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2] Skipping beta releases?
On 7/3/05, Andreas Jung [EMAIL PROTECTED] wrote: the current release model of Zope 2 is based on doing at least one beta release for minor releases (Zope 2.7.X where X 0). I have the strong impression that beta releases are not adopted and tested by most people. They usually use the final version of a release. So most bugs are discovered in final releases and not in beta releases. People interested in the most current version can and do download the sources from the CVS or SVN. So I propose to skip beta releases for minor releases in the future. Alpha and beta releases are fine for major releases. Beta releases for a minor release can be made if there are some changes or fixes that must be tested by people. Any comments? For pure bugfix releases, unless the bugfixes are expected to have side-effects, then a beta is not needed, you are right. Skipping betas may mean that you need to make more non-beta releases, but then that's still less work. :-D -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Zope-Checkins] CVS: Packages/ZODB - FileStorage.py:1.135.6.9
[Chris Withers] O... is this surfaced through the Zope undo tab? Try it. I'm sure that was Dieter's intent: http://mail.zope.org/pipermail/zodb-dev/2003-October/006157.html ,,,' The patch also enhances FileStorage and lets its UndoSearch._readnext provide information about the transaction size. This is very valuable when you want to spot strange transaction sizes via Zope's Undo tab (much more convenient than fsdump) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] bridging Zope core interfaces - a small proposal
Hi! Five comes with some code that bridges Zope 2 interfaces to Zope 3 interfaces. This way Zope 2 interface definitions can be reused without adding redundant code. This is quite useful, but doesn't work for Zope core interfaces: Five depends one many Zope core packages and using Five code in these packages creates circular imports. I propose to move the Five bridging code (bridge.py, fiveconfigure.createZope2Bridge and related tests) to the Interface package of Zope 2. Five would still ship with a copy of that code for Zope 2.7 backwards compatibility. Any comments? If there are no objections, I'll check in these changes. Cheers, Yuppie ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] bridging Zope core interfaces - a small proposal
On 7/6/05, yuppie [EMAIL PROTECTED] wrote: Five comes with some code that bridges Zope 2 interfaces to Zope 3 interfaces. This way Zope 2 interface definitions can be reused without adding redundant code. This is quite useful, but doesn't work for Zope core interfaces: Five depends one many Zope core packages and using Five code in these packages creates circular imports. Did I understand that correctly, it is a problem if you want to use Five *from* zope core code? ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: bridging Zope core interfaces - a small proposal
Lennart Regebro wrote: On 7/6/05, yuppie [EMAIL PROTECTED] wrote: Five comes with some code that bridges Zope 2 interfaces to Zope 3 interfaces. This way Zope 2 interface definitions can be reused without adding redundant code. This is quite useful, but doesn't work for Zope core interfaces: Five depends one many Zope core packages and using Five code in these packages creates circular imports. Did I understand that correctly, it is a problem if you want to use Five *from* zope core code? Correct. It's not always a problem, but the bridging code doesn't depend on anything else in Five, so I guess moving that code into the core would be a clean solution. Cheers, Yuppie ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: bridging Zope core interfaces - a small proposal
On 7/6/05, yuppie [EMAIL PROTECTED] wrote: Lennart Regebro wrote: Did I understand that correctly, it is a problem if you want to use Five *from* zope core code? Correct. It's not always a problem, but the bridging code doesn't depend on anything else in Five, so I guess moving that code into the core would be a clean solution. Well, we wanna start doing that in Zope 2.9, so +1 on svn head from me I guess. :) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
