E&S CVS Commit: PEAK - Fixed the problem where Persistent.__class__ always had to be first in a

pje at eby-sarna.com pje at eby-sarna.com
Sun Nov 3 20:22:00 EST 2002


Module Name:	PEAK
Committed By:	pje
Date:		Mon Nov  4 01:21:34 UTC 2002

Modified Files:
	PEAK/src/Persistence: cPersistence.c
	PEAK/src/peak/model: api.py

Log Message:
Fixed the problem where Persistent.__class__ always had to be first in a
list of base classes for a metaclass.  Note that Persistent.__class__
(or any class derived therefrom) should always be listed *last* in a list
of metaclass bases, if any of the Python metaclasses have a  __new__
method.  Otherwise, some Python __new__ methods may be skipped when
creating a class from the metaclass.  PEAK rarely uses metaclass __new__
methods, however, and fewer still such metaclasses will ever need to be
mixed with Persistent.__class__.  But it still merits caution.


To view diffs of this commit, you can use the following URL(s):
http://cvs.eby-sarna.com/PEAK/src/Persistence/cPersistence.c.diff?r1=1.2&r2=1.3
http://cvs.eby-sarna.com/PEAK/src/peak/model/api.py.diff?r1=1.33&r2=1.34

To generate a diff of this commit:
cvs rdiff -r1.2 -r1.3 PEAK/src/Persistence/cPersistence.c
cvs rdiff -r1.33 -r1.34 PEAK/src/peak/model/api.py

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.




More information about the source-changes mailing list