Message5526

Author juneau001
Recipients juneau001, slucas
Date 2010-02-14.15:58:13
SpamBayes Score 6.69751e-08
Marked as misclassified No
Message-id <1266163095.3.0.807254097281.issue1551@psf.upfronthosting.co.za>
In-reply-to
Content
A workaround to make shallow copies of native Java objects is to use the Java clone() technique.  In order to repair this issue and ensure that the Jython interpreter does not treat copies of native Java objects using copy.copy as proxy classes, we'll have to somehow alter the proxy objects (or perhaps the copy lib) to perform a check to see if indeed the object being copied is a native Java object.  If it is a native Java object, then treat differently then a Python object that inherits from a Java class.  

Perhaps the easiest fix would be to place a check in the copy lib that would simply use clone() as opposed to copy.copy if an object is found to be a native Java object.  The most difficult part of the problem is determining if an object is indeed native Java or a Python class that inherits from a Java object.
History
Date User Action Args
2010-02-14 15:58:15juneau001setmessageid: <1266163095.3.0.807254097281.issue1551@psf.upfronthosting.co.za>
2010-02-14 15:58:15juneau001setrecipients: + juneau001, slucas
2010-02-14 15:58:15juneau001linkissue1551 messages
2010-02-14 15:58:13juneau001create