From: Steven Yi <ste...@gm...> - 2005-07-19 10:16:57
|
Hi All, Thanks very much for your thoughts on my issues. I'm very happy to say that upgrading to the Jython2.2alpha1 seems to have solved my problems and I no longer get the deepcopy and other issues which were coming up sporadically. I guess it was that the version of jython I had just didn't run well with Java 5 (?). Thanks also to the Jython dev team for putting out 2.2alpha1! It's a great accomplishment and i'm eager to start exploring all the work you have all put in. steven On 7/11/05, Ed Korthof <ed...@ap...> wrote: > On Sun, Jul 10, 2005 at 01:58:56PM -0400, Updike, Clark wrote: > > I thought copy.py was something you wrote, so > > you may be right that it's something more subtle. > > But my suggestion still might help you debug it. >=20 > The copy.py which I see has no mutex protections. Use mutex in your > application for things like copying objects; otherwise threads will run > over each other. >=20 > http://www.python.org/doc/2.3/lib/module-mutex.html >=20 > copy.py doesn't look like it is the right place for mutexes. In this > case, my guess would be that the code feeding objects to copy.py is > modifying the objects at the same time that copy.py is working on them; > there's no way to correct for that w/in copy.py. >=20 > good luck -- >=20 > Ed >=20 > |