 |
 |
 |
S60 Module Reference |  |
 |
 |
|
|
|
S60 Module Reference | |
|
|
Limitations:
1. On this platform, the stack size is significantly less compared to other platforms and hence deep recursions and high memory consuming operations may cause stack overflow.
2. Calling setsockopt() on UDP sockets requires that the application is signed with NETWORKCONTROL capability.
3. The file access time and modification time are same on Symbian and the same behavior is reflected in the utime module.
4. Support for touch enabled devices is limited. Touch events other than LSK and RSK are not handled. Hence the UI handling in modules like graphics, glcanvas and appuifw will not function as expected on touch enabled devices.
Bugs:
1. Floating point formatting/parsing routines on this platform are imprecise and as a result you can't round-trip floating point numbers reliably or rely on floating point constants in Python source code to be precisely parsed into their corresponding double values.
2. The strftime() API in the OpenC library returns output parameters with junk characters when the 'Z' format specifier is used with the timezone as NULL and hence few test-cases for time and strptime modules fail.
3. The connect() API in the OpenC library raises EEXISTS instead of EISCONN, when it is called on an already connected non-blocking TCP socket.
4. Problem with decimal separator when the phone's locale uses a decimal separator other than dot ('.')
5. time.clock() does not work as expected.
6. APIs in extension modules which use callbacks does not work if invoked from a thread.
7. sensor module is not supported on S60 3rd edition FP2 and 5th edition devices.
8. For applications packaged with s60ui profile, 'Exit' key does not work as expected when raw_input is pending.
9. The document of the extension modules are not fully in line with the new code base.
10. Importing modules under application's private directory fails.
A work around for this problem is packaging the modules to a directory under
\data\python and include this directory path into sys.path before
importing the modules. Ensymlbe's -extrasdir option can be used to place the modules under the required directory.
For example :
a)Place default.py in the directory "root\default.py"
b)Place dependent modules in "root\extras\data\python\
c)In default.py update the sys path
import sys
sys.path.append("c:\\data\\python")
d)ensymble py2sis root -extrasdir=extras
where "root" is the directory which contains default.py and "extras"
directory. "extras" directory contains the required modules under the
required directory tree.
Failing test cases:
Below is the summary of the standard regrtest Python module executed on this platform.
|
Skipped test cases:
These tests are skipped as one or more modules needed by them are not supported on this platform.
These tests are also skipped, but are related to the zipping of all the standard Python files.
|
|
|
|
S60 Module Reference | |
|
|