Python Console does not show results

g0dsgif1 / python-for-android

Automatically exported from code.google.com/p/python-for-android

Apache License 2.0

0 stars 0 forks source link

Python Console does not show results #27

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Running any python script on the particular device (m701 tablet) no text is 
output to the console display but example scripts appear to run.  This does not 
occur on other device, output data is printed to console without problems.

What is the expected output? What do you see instead?
Output is not shown in console.

What version of the product are you using? On what operating system?
Using:
sl4a_r4.apk
PythonForAndroid_r4.apk
python_r16.zip
python_scripts_r13.zip
python_extras_r14.zip
On android 2.3.3

Please provide any additional information below.

Original issue reported on code.google.com by onlinetimc@gmail.com on 28 Sep 2011 at 11:15

GoogleCodeExporter commented 8 years ago

I encounterd this issue too.
My platform is x86, and when i open the Python interpreter there is nothing on 
the screen.
Anyone know how to fix this issue?

Original comment by beyond...@gmail.com on 24 Oct 2011 at 7:44

GoogleCodeExporter commented 8 years ago

I'm experiencing the same problem on a "Touchlet X4". I can successfully run 
scripts, i.e. start them from the Scripts-View. I tried different examples like 
"speak.py" and "hello_world.py" and some of my own scripts. All work great, but 
there is no console-output.
If you start the interpreter directly, there is just a blank console window 
with a cursor. You can write commands and execute them, but there is no console 
output.

I tried different versions of sl4a (r3 and r4) and Python for Android (r4, r6, 
r7b1), which changes nothing. Reinstalling does not solve the problem, either.

It might be the same problem as described in Issue #28. It would be great to 
see a solution here.

Original comment by daniel.s...@googlemail.com on 26 Jan 2012 at 7:53

GoogleCodeExporter commented 8 years ago

I retried this with the device which failed previously, but running a totally 
different ROM (was 2.3 now 2.1, probably totally different kernel) and I get 
the very same result.

Hopefully that helps with working out what the cause could be.  Still works 
fine on my other device.

Original comment by onlinetimc@gmail.com on 9 Feb 2012 at 3:42