I have a custom portable python install that works really nice and running editra. My only "oops" is that launch don't work.
When I click the run button, I got:
The requested command could not be executed.
>>> Exit Code: -1
Editra log gives me:
[10:14:57][Launch][info] Starting process [10:14:57][launch][err] error decoding log message string [10:14:57][Launch][info] Found commands [u'pylint', u'pylinterr', u'python']
I PyShell, I can see I'm at right directory:
Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information.
>>> import os >>> os.path.abspath(os.path.curdir)
'I:\\Programas\\Python'
My python executable is on this directory (I: is a usb stick).
On Tue, Apr 3, 2012 at 8:19 AM, Tomas Schertel <tscher...@gmail.com> wrote: > Hi guys.
> I have a custom portable python install that works really nice and running > editra. > My only "oops" is that launch don't work.
> When I click the run button, I got:
> The requested command could not be executed. >>>> Exit Code: -1
> Editra log gives me:
> [10:14:57][Launch][info] Starting process > [10:14:57][launch][err] error decoding log message string > [10:14:57][Launch][info] Found commands [u'pylint', u'pylinterr', u'python']
> I PyShell, I can see I'm at right directory:
> Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on > win32 > Type "help", "copyright", "credits" or "license" for more information. >>>> import os >>>> os.path.abspath(os.path.curdir) > 'I:\\Programas\\Python'
> My python executable is on this directory (I: is a usb stick).
> What can I do to have launch working?
What version of Editra and what version of Launch are you using?
Have you tried configuring the full path to your executable to see if that works? Either that or add I\Programas\Python to your PATH variable to ensure its on your path.
Launch always sets the working directory of the other process to the location of the file that is being run in it so Editra may be in I\Programas\Python but the spawned shell process is probably elsewhere.
> > Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit > (Intel)] on > > win32 > > Type "help", "copyright", "credits" or "license" for more information. > >>>> import os > >>>> os.path.abspath(os.path.curdir) > > 'I:\\Programas\\Python'
> > My python executable is on this directory (I: is a usb stick).
> > What can I do to have launch working?
> What version of Editra and what version of Launch are you using?
> Have you tried configuring the full path to your executable to see if > that works? Either that or add I\Programas\Python to your PATH > variable to ensure its on your path.
> Launch always sets the working directory of the other process to the > location of the file that is being run in it so Editra may be in > I\Programas\Python but the spawned shell process is probably > elsewhere.
On Tue, Apr 3, 2012 at 9:42 AM, Tomas Schertel <tscher...@gmail.com> wrote: > Hi Cody.
> I'm using Editra 0.6.99 and Launch 1.12. > I also have a few lines of batch code initializing my environment:
<snip>
> Using Editra's PyShell to see my environment variables > (os.environ.iteritems), I got the right values.
Have you tried setting the full absolute path to the executable your trying to run in your Launch configuration to see if it acts any differently?
If it still doesn't work then please set the Editor mode to Verbose Debug (see pref dialog) then try to run Launch again and see if there are any different errors printed to the log window or log file (editra.xxxxxx.log in your temp directory).
I did put full path to python executable but I got same error. Changing Editra to verbose debug and calling Launch to run my code, I got this error message on Editra Log:
[12:05:39][Launch][info] Starting process [12:05:39][launch][err] error decoding log message string [12:05:39][launch][err]Traceback (most recent call last): [12:05:39][launch][err] File "i:\programas\python\lib\site-packages\editra\plugins\launch-1.12-py2.7.egg \launch\launch.py", line 685, in DoProcessError [12:05:39][launch][err] util.Log(u"[launch][err] %s" % excdata) [12:05:39][launch][err]UnicodeDecodeError: 'ascii' codec can't decode byte 0xe1 in position 27: ordinal not in range(128) [12:05:39][Launch][info] Found commands [u'pylint', u'pylinterr', u'python']
On Tuesday, 3 April 2012 11:53:08 UTC-3, Cody Precord wrote:
> Hi,
> On Tue, Apr 3, 2012 at 9:42 AM, Tomas Schertel <tscher...@gmail.com> > wrote: > > Hi Cody.
> > I'm using Editra 0.6.99 and Launch 1.12. > > I also have a few lines of batch code initializing my environment:
> <snip>
> > Using Editra's PyShell to see my environment variables > > (os.environ.iteritems), I got the right values.
> Have you tried setting the full absolute path to the executable your > trying to run in your Launch configuration to see if it acts any > differently?
> If it still doesn't work then please set the Editor mode to Verbose > Debug (see pref dialog) then try to run Launch again and see if there > are any different errors printed to the log window or log file > (editra.xxxxxx.log in your temp directory).
On Tuesday, 3 April 2012 12:07:48 UTC-3, Tomas Schertel wrote:
> I did put full path to python executable but I got same error. > Changing Editra to verbose debug and calling Launch to run my code, I got > this error message on Editra Log:
> [12:05:39][Launch][info] Starting process > [12:05:39][launch][err] error decoding log message string > [12:05:39][launch][err]Traceback (most recent call last): > [12:05:39][launch][err] File > "i:\programas\python\lib\site-packages\editra\plugins\launch-1.12-py2.7.egg \launch\launch.py", > line 685, in DoProcessError > [12:05:39][launch][err] util.Log(u"[launch][err] %s" % excdata) > [12:05:39][launch][err]UnicodeDecodeError: 'ascii' codec can't decode byte > 0xe1 in position 27: ordinal not in range(128) > [12:05:39][Launch][info] Found commands [u'pylint', u'pylinterr', > u'python']
> On Tuesday, 3 April 2012 11:53:08 UTC-3, Cody Precord wrote:
>> Hi,
>> On Tue, Apr 3, 2012 at 9:42 AM, Tomas Schertel <tscher...@gmail.com> >> wrote: >> > Hi Cody.
>> > I'm using Editra 0.6.99 and Launch 1.12. >> > I also have a few lines of batch code initializing my environment:
>> <snip>
>> > Using Editra's PyShell to see my environment variables >> > (os.environ.iteritems), I got the right values.
>> Have you tried setting the full absolute path to the executable your >> trying to run in your Launch configuration to see if it acts any >> differently?
>> If it still doesn't work then please set the Editor mode to Verbose >> Debug (see pref dialog) then try to run Launch again and see if there >> are any different errors printed to the log window or log file >> (editra.xxxxxx.log in your temp directory).
On Mon, Apr 9, 2012 at 11:57 AM, Tomas Schertel <tscher...@gmail.com> wrote: > Hi Guys. Any news on this issue?
Sorry, no haven't had much time recently. Please open a ticket in the issue tracker with the information about the problem and the error.
Unfortunately the error message seems to be failing to display due to an encoding error, so difficult to determine the original error. One thing you could test is that the executable your trying to run and the file/script it is running on using a path for both that does not contain any extended ascii characters (umlauts, ect..) just to make sure if it is an encoding issue or not.
Also what is the exact command posted to the Launch window (in the blue text at the top)?
