[tvijayan]

Python for S60 1.9.2 is now released.

You can download the release from maemo garage
https://garage.maemo.org/frs/?group_id=854

This release runs on S60 3rd edition, S60 3rd edition FP1, S60 3rd edition FP2 and S60 5th edition devices.

The release includes:
- Self signed device binaries for S60 3rd Ed and S60 3rd Ed FP2 (which will work even on S60 3rd Ed FP1 and S60 5th Ed devices respectively).
- unsigned device binaries for S60 3rd Ed and S60 3rd Ed FP2 (which will work even on S60 3rd Ed FP1 and S60 5th Ed devices respectively).
- Separate SDK zips for 3rdEd, 3rdEdFP1 and 3rdEdFP2. SDK zip contains both gcce and armv5 link libraries
- Installer for Windows platform that includes
----- Getting started guide
----- selfsigned PyS60 runtime sis
----- selfsigned PythonScriptShell sis
----- Application packaging tool with GUI and README
----- Python HTML documentation updated with S60 module reference
----- sensor module documentation for S60 3rd Ed FP2 and S60 5th Ed.
- Archive package for Linux/Mac that includes
----- selfsigned PyS60 runtime sis
----- selfsigned PythonScriptShell sis
----- Application packaging tool with README
----- Python HTML documentation updated with S60 module reference
- Python source code
- OpenSSL source code. This source code is released just to be in complaint with the terms of LGPL licensed software. This source code is
nothing to do with PyS60 software.

sensor module is now available for accessing the sensors on S60 3rd Ed FP2 and S60 5th Ed devices that have S60 Sensor Framework libraries. The existing sensor scritps has to be rewritten using the new module to make it work on S60 3rd Ed FP2 and S60 5th Ed. The rewritten sensor scripts will not work on S60 3rd Ed and S60 3rd Ed FP1 devices, the support for the same will be provided in the consecutive dot releases. The existing sensor applications will still work on S60 3rd Ed and S60 3rd Ed FP1 devices without any change.

The selfsigned Python runtime component and the PythonScriptShell packages are available with the user-grantable capability set.
The capability set for S60 3rd Ed is ReadUserData WriteUserData NetworkServices LocalServices UserEnvironment.
The capability set for S60 3rd Ed FP2 is ReadUserData WriteUserData NetworkServices LocalServices UserEnvironment Location.

The unsigned Python runtime component and the PythonScriptShell packages are available with high capability set.
The capability set is LocalServices NetworkServices ReadUserData WriteUserData UserEnvironment Location PowerMgmt ProtServ SwEvent SurroundingsDD ReadDeviceData WriteDeviceData TrustedUI

The UID of Python runtime is changed to 0xE0201514.

Expectation management: THIS IS NOT A FINAL PRODUCT.

This is one of the rough releases of a code-base that has been rewritten to a large extent. Just like we did with the 1.1.x and 1.3.x
series. We want to involve you in the development and testing process so that you can point out any sharp edges and pointy bits that the releases may have.

The idea is to expose the code to early testing and gather feedback so that the final PyS60 2.0 can be solid and fulfill YOUR needs.

Now, on to what we have now - the 1.9.2 release.

On the brighter side:

- sensor module support for accessing the sensors on the devices that have
S60 Sensor Framework libraries. This module's API compatibility between 1.9.x
versions isn't guaranteed until 2.0. It won't be broken without good reason,
but it can happen. Refer to the sensor-module-specifications.doc available
from the installer for more details.

- Reduction in the installer size!
The application packager GUI is now based on Tkinter, hence PyQt setup is
removed from the windows installer.

- The UID of PythonRuntime has changed from '0xF0201514' to '0xE0201514'

- PyS60 Application Packager is now based on ensymble 0.28

Here are some of the things that are worse in 1.9.2 when compared to 1.4.5:

- The runtime package is much bigger than with 1.4.x. This'll get smaller once we have the modified packaging model working - estimate is that
the final base runtime would be less than 1MB.

- There is an additional dependency to the OpenC libraries, which must be installed for the runtime to work.

- Sadly, S60 2.x devices are not supported by the new code-base, and never will be. This is because OpenC libraries aren't available for S60 2.x.

- Binary compatibility between 1.9.x versions isn't guaranteed until 2.0. We won't break it without good reason, but it can happen.

- API compatibility of new sensor module isn't guaranteed until 2.0. We won't break it without good reason, but it can happen.

Our targets for the final 2.0 are:

- Better usability for the developer and the end user:

- Easier runtime deployment. It must be possible for a developer to package their application in a way that the end user doesn't need
to think about the runtime installation. Note that we're not saying the end user doesn't have to _install_ the runtime, we're just saying
they don't need to _think_ about it.

- Easier tools installation and SIS packaging for Python applications. Especially packaging Python applications to SIS has proved to be pretty
tough with all the dependencies you need to install. The 1.9.0 release improves things with the new all-in-one installer that gives you the
packaging tool, the documentation and the SIS files you need for development in one package. The user-friendly Ensymble tool is now official,
and there is a GUI for one-button package creation.

- Easier and more robust ways to use and distribute 3rd party extension modules with your application. Free use of third party extensions is
one of the main advantages of Python, and we want to enable and encourage that. We'll improve the Ensymble packaging tool to automatically
bundle modules not included in the base runtime into your application SIS, as well as specify how a module author can distribute their
module to other developers so that the module can be easily used.

- Integrated HTML documentation: The S60 specific documentation is now a part of the full Python documentation so you no longer need to switch
between them.

- Reliability and compliance with the standard Python. We've put effort into automatic testing on multiple target platforms as well as fixing
any noncompliance revealed by Python's own regrtest.py test suite. The compliance isn't perfect yet, but it's much better than with the old
1.4.x code-base.

- Quicker start-up and smaller base runtime package size than with 1.9.0.

- Selected API additions. Qt support is definitely on the roadmap. Schedule we can't give yet.

- Support for non-Windows platforms for things other than C++ extension development. Already preliminary support is available in 1.9.0, which
contains an all-in-one archive that gives you the packaging tool, the documentation and the SIS files.

Bug reports, patches and feature requests can be filed in mamemo garage. That's what we track regularly, not every thread in the discussion
board. If you post a bug report only in the DiBo, we might miss it.

Bugs: https://garage.maemo.org/tracker/?at...54&func=browse
Feature Requests: https://garage.maemo.org/tracker/?at...54&func=browse
When filing bugs, include the device you used, its firmware version (you can see this by entering *#0000# in the idle screen), the PyS60 version
and a minimal test case (if applicable).

For more details on reporting bugs refer the "Reporting Bugs" section of the Python documentation.

That's it for now. Try it out, send feedback and stay tuned for 1.9.3.

Happy hacking!

-- Python for S60 team

[gaba88]

hello PyS60 Team

Great to see the new release and the best part in it is the availability of the new sensor module.

Keep it up and we all are waiting eagerly for the stable PyS60 2.0.

Enjoy Pythoning
Gaba88

[croozeus]

Sensor framework - thanks!

Babysteps are not bad at all if we do get a polished product in the end!

Can't wait for the touch UI support

Cheers,
Croozeus

[aaaaapo]

Originally Posted by croozeus

Sensor framework - thanks!

Yes, tested in N82 and verlet.py, sensor_analyzer.py etc., works as in 1.4.5. (Hello JOM! :-)

Originally Posted by croozeus

Babysteps are not bad at all if we do get a polished product in the end!

Release early, release often (or how it is)... I like see minor releases more often than giant leaps every 6 months. (At least I see someone is doing something. :-)

[croozeus]

Originally Posted by aaaaapo

I like see minor releases more often than giant leaps every 6 months. (At least I see someone is doing something. :-)

I agree! Just what the photo on this link signifies.

[jtullis]

I cannot find the s60 pdf doc for 1.9.2. I have installed the exe on my pc so I have the html files file:///C:/Program%20Files/PythonForS60/doc/s60/s60.html but this is no good as I want the pdf so I can search fulltext. Where can I download the pdf documentation, like it was easy before? Thanks

[gaba88]

hello jtullis

AFAIK the new releases have only html documentation they no more have pdf documentation.

Enjoy Pythoning
Gaba88

[jtullis]

Oh no!!! So how do I search fulltext? There are so many pages to look through, and the index doesn't list every instance of every keyword! This could be a backwards step unless someone can help me!

[croozeus]

Originally Posted by jtullis

Oh no!!! So how do I search fulltext? There are so many pages to look through, and the index doesn't list every instance of every keyword! This could be a backwards step unless someone can help me!

The old 1.4.5 documentation still exists! I use that for PyS60 modules.

[JOM]

Originally Posted by aaaaapo

Yes, tested in N82 and verlet.py, sensor_analyzer.py etc., works as in 1.4.5. (Hello JOM! :-)

Hello aaaaapo

Good news, will have to install PyS60 1.9.x finally! Recently checked how 1.4.5 works in 5800, but even listbox didn't work! Have to check how backwards compatible 1.9.x will be in older devices...

Cheers,

--jouni

[Rafael T.]

I really liked this release! Not only because of the Sensor Framework support, but also because we can see that you guys are making often and minor release, walking step-by-step, attempting to make up to our requests


Thanks,

Rafael.

[marcelobarrosalmeida]

The best phrase in this announce in my humble opinion was “Qt support is definitely on the roadmap”!
Great job !

[Yerghi]

I tried FP2 and FP1 version and sensor module doesn't work on Nokia E66.

[gaba88]

Originally Posted by Yerghi

I tried FP2 and FP1 version and sensor module doesn't work on Nokia E66.

hello Yerghi

welcome to forum nokia python discussion boards.

it will be great if you throw some more light on what problem you are facing with the module. I mean what sort of errors you are getting.

Enjoy Pythoning
Gaba88

[Yerghi]

In FP1 version I can't import sensor module.("ImportError: No module named _sensor")
In FP2 version I can import sensor module but if I run some function it gives me "SymbianError: [Errno -46] KErrPermissionDenied".

Thanks