Issue2448
Created on 2015-12-30.06:44:19 by latifrons, last changed 2016-01-28.16:01:35 by zyasoft.
|
| msg10574 (view) |
Author: latifrons (latifrons) |
Date: 2015-12-30.06:44:18 |
|
import sys
jython = sys.executable.replace('/bin/jython','')
sys.path.append(jython + '/Lib/site-packages')
print sys.path
|
| msg10577 (view) |
Author: Jim Baker (zyasoft) |
Date: 2016-01-02.05:01:52 |
|
I'm not certain which debugger you are referring to. There's really only one standard Python debugger, pdb. So trying out a simple test script:
print "Before pdb"
import pdb; pdb.set_trace()
print "After pdb"
this will break into pdb, at which point I can try looking at sys.path (contains site-packages) as well as 'site' in sys.modules.
In general, the site module - which adds site-packages to sys.path - is imported by default when Jython starts up, even when not used from the command line. This was a change as of 2.7.0. Such import can be turned off with the -S option (or equivalently, Options.importSite = False).
|
| msg10654 (view) |
Author: Jim Baker (zyasoft) |
Date: 2016-01-15.15:30:27 |
|
To my knowledge, all Python source-level debugging tools use the facilities provided for pdb, using sys.settrace. (Jython also supports some views from Java level debugging, but this is much more limited - no direct knowledge of Python, just corresponding source lines to underlying bytecode.)
|
|
| Date |
User |
Action |
Args |
| 2016-01-28 16:01:35 | zyasoft | set | status: pending -> closed |
| 2016-01-15 15:30:27 | zyasoft | set | status: open -> pending
resolution: works for me
messages:
+ msg10654 |
| 2016-01-02 05:01:53 | zyasoft | set | nosy:
+ zyasoft
messages:
+ msg10577 |
| 2015-12-30 06:44:19 | latifrons | create | |
|
