jEdit Community - Resources for users of the jEdit Text Editor
JPyDebug doesn't work
Submitted by misterdanny on Tuesday, 26 June, 2007 - 01:36
I installed this in hope of being able to work with python in jedit (i need something to check for errors) on the "error list" window it only shows

"1: Python Source Insepctor launch error = IOException when building process : CreateProcess: ....." then theres a long string of different file locations then at the very end it says error=2

I think something is setup wrong but I went through every menu to see what setting might be wrong to cause this and I couldn't find anything. This shows up even if the file is empty or if all it says is print 'hi' or something.

Any ideas? or alternatives to python error checking in jedit?
Comment viewing options
Select your preferred way to display the comments and click 'Save settings' to activate your changes.
Re: JPyDebug doesn't work
by frred on Thu, 01/11/2007 - 01:32
I had a hard time setting up JPyDebug on Windows XP. When I
previously had used it on Debian Linux it seemed easier...

First of all I ended up getting an old Version of JPyDebug from
the JEdit website (where you can download all the plugins).
Then I got the Python Source Inspector launch errors.
Setting the paths to my Python installation and Java solved some
of those issues. But still nothing would work except for syntax
checking. Placing a jython.jar in Jedit's jar folder did not help
much.

Worst of all was the popup error message that Beanshell encountered
an error whenever I tried to run JPyDebug!
java.lang.NoSuchMethodError:
org.gjt.sp.jedit.textarea.JEditTextArea.getBuffer()
Very strange, because the JEdit API shows that the
method in question is known and line 362 in
org.jymc.jpydebug.jedit.PythonJeditPanel.install() is syntactically
correct!

Finally I got rid of the 0.0.16 Version of JPyDebug. And
that seemed to do the trick. Runs like a charm now.

For all those of you who want to save some time and get that
JpyDebug to run on their systems, here is how. Hope it works for you:)

--------------------------------------------------------
---------------------- HOWTO ---------------------------

Get the latest jpydebug version from sourceforge. (sourceforge.net/projects/jpydbg/)

I also found the news at jpydbg.blogspot.com interesting.
It seems that the documentation provided with jpydebug itself
is the latest version. You can read it after "installing" jpydebug
by clicking the help-button on the plugin-manager of JEdit.
(This should work even everything else fails...)

What you need:

- jpydebug itself. Version jpydebug-jedit42-0.0.18-5.jar works for me.
(If you have Jedit4.3 then get the jedit43 file version.)
Move the jpydebug jar file as is (no need to unpack or rename
anything) into your Jedit jar folder (I prefer systemwide
plugin installation. If you use user-specific installation then
move the file wherever your other plugins are).

- jython.jar. Get it from the Jython official Project Home.
I used version 2.2.1. When you download Jython you get a huge
installer jar. You do NOT have to install it. Simply extract
from within the jar one of the files: "jython.jar".
Place that file in your JEdit jar folder (or wherever you put
your plugins.) You also do NOT need the jython plugin for Jedit!
In fact there seems to be some kind of inconsistency with it
concerning sidekick when used with jpydebug.

-Of course you need a Java runtime environment. But since you are
using Jedit already, we can skip this.... I used JRE 1.5 or 1.6.

-Are the environment variables set? On Windows XP use Control-Panel
-->System Settings --> Advanced --> Environment Variables.
Set JEDIT_HOME as well as JAVA_HOME

-Restart Jedit to install jpydebug.

-Set the JPyDebug options!
I did not install Jython or the Jython plugin for Jedit! So I will
skip anything related to that.
What you have to do though is set up CPython:
Specify where your python.exe (Windows again...) is, and the paths
to python/dlls, python/Lib, ...
Also, even if you do not want to use Jython, nonetheless specify the
path to jython.jar in the JPython options. Also set the path to
the java.exe (windows...).

-You may have to restart JEdit again after setting the options!!!


(I also had a very strange problem, where the admin account was
unable to set the options (Jpydebug would never save them), but the
user account was fully functional in that respect. Weird.
Another problem I ran into was JEdit becoming unresponsive when
using utf-8 unicode strings in dicts and running with JpyDebug
but had no problems with python on the commandline. Maybe unrelated.)

Frred
User login
Browse archives
« November 2014  
MoTuWeThFrSaSu
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Poll
Are you interested in language packs for jEdit?
Yes, and I could help maintain translations
26%
Yes, I'd like to have translations
33%
Indifferent
35%
No, that'd be bad (please comment)
7%
Total votes: 1092
Syndication
file   ver   dls
German Localization light   4.4.2.1   47229
Context Free Art (*.cfdg)   0.31   37206
JBuilder scheme   .001   11572
R Edit Mode - extensive version   0.1   11397
BBEdit scheme   1.0   11137
ColdFusion scheme   1.0   11126
Advanced HTML edit mode   1.0   10849
Matlab Edit Mode   1.0   10714
jEdit XP icons   1.0   10174
XP icons for jEdit   1.1   9967