[ grinder-Bugs-3464533 ] DCR instrumentation of bound PyMethods
SourceForge.net <[email protected]> Fri, 23 Dec 2011 09:49:04 -0800
| Newsgroups | gmane.comp.java.grinder.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #3464533, was opened at 2011-12-23 09:49 Message generated for change (Tracker Item Submitted) made by philipa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3464533&group_id=18598 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core engine Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: Philip Aston (philipa) Assigned to: Nobody/Anonymous (nobody) Summary: DCR instrumentation of bound PyMethods Initial Comment: PyMethod DCR instrumentation is broken: 1. Jython implementations use multiple different objects to refer to the same bound PyMethod. The DCR instrumentation is based on the identity of the target object, and not the equality. 2. Jython 2.2 appears to implement calls from an instance to itself (self.foo()) using a PyFunction. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=118598&aid=3464533&group_id=18598 ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev