Re: ZPatterns (sub-)transaction problems
"Phillip J. Eby" wrote:
I will try to have a ZPatterns snapshot release made this week that will include those fixes (plus the fix for a problem with DynPersist that we also discovered yesterday).
Great. I'm looking forward to that. Can we lose DynPersist altogether for this release? Or are there still folks out there using ZPatterns with 2.1.6? -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net
At 03:56 PM 9/14/00 +0100, Steve Alexander wrote:
Can we lose DynPersist altogether for this release?
Unfortunately, no. Zope's cPersistent class appears it may have a bug that is roughly similar to the one we're fixing in DynPersist. (i.e., not calling __of__ or other binding operations on an object returned from __getattr__) I've written Jim to ask whether my interpretation of that code is correct, but have not received a reply. It may take a new Zope release before DynPersist is able to go away. :(
Or are there still folks out there using ZPatterns with 2.1.6?
Support for 2.1.x was officially dropped with ZPatterns 0.4.2a1, but in practice most of the support code is still there today. It's just that I've stopped testing on 2.1.x and no longer write code with 2.1.x compatibility in mind. The re-architecting of the transaction machinery will *require* 2.2.x's transaction ordering semantics.
It's up now. In addition to the transaction fixes and DynPersist fix, this release also fixes the missing import of aq_base in PlugIns.py, and the SkinScript compiler fouling up certain expressions due to its removal of spaces between tokens. Last, but not least, you can now place Specialists inside other Specialists without getting an error. At 03:56 PM 9/14/00 +0100, Steve Alexander wrote:
"Phillip J. Eby" wrote:
I will try to have a ZPatterns snapshot release made this week that will include those fixes (plus the fix for a problem with DynPersist that we also discovered yesterday).
Great. I'm looking forward to that.
Phillip J. Eby wrote:
It's up now. In addition to the transaction fixes and DynPersist fix, this release also fixes the missing import of aq_base in PlugIns.py, and the SkinScript compiler fouling up certain expressions due to its removal of spaces between tokens. Last, but not least, you can now place Specialists inside other Specialists without getting an error.
According to diff, there is no difference between DynPersist.c in the latest release, and DynPersist.c in 0-4-2a1. The dates on the files are both Apr 26 too. -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net
At 05:39 PM 9/14/00 +0100, Steve Alexander wrote:
Phillip J. Eby wrote:
It's up now. In addition to the transaction fixes and DynPersist fix, this release also fixes the missing import of aq_base in PlugIns.py, and the SkinScript compiler fouling up certain expressions due to its removal of spaces between tokens. Last, but not least, you can now place Specialists inside other Specialists without getting an error.
According to diff, there is no difference between DynPersist.c in the latest release, and DynPersist.c in 0-4-2a1.
The dates on the files are both Apr 26 too.
Oops! It's fixed now. Everyone please note that the correct file size for ZPatterns-0-4-2a2.tgz is 47,811 bytes, not 47,756. Sorry about the mix-up; Ty and I missed a few files in the tagging process prior to generating a release. :(
ZPatterns 0.4.2 alpha 3 is now available. It fixes all bugs that I know of at the present time (both reported on the lists and found during our own usage/testing), and adds one feature: a decent sized screen for editing SkinScript! This release does not yet have the overhaul of transaction handling that I'm planning for a future release (probably 0.4.3). So the use of subtransactions in the same transaction where DataSkins are being manipulated is still potentially problematic if more than one subtransaction commit occurs, or a (sub)transaction is aborted.
participants (2)
-
Phillip J. Eby -
Steve Alexander