Python for S60 1.9.1 is now released.

You can download the release from maemo garage

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).
- 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
----- PyS60 runtime sis
----- PythonScriptShell sis
----- Application packaging tool with GUI and README
----- Python HTML documentation updated with S60 module reference
- Archive package for Linux/Mac that includes
----- PyS60 runtime sis
----- PythonScriptShell sis
----- Application packaging tool with README
----- Python HTML documentation updated with S60 module reference
- Python source code
- OpenSSL source code
- PyQt source code

The Python runtime component and the PythonScriptShell packages are self signed 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.

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.1 release.

On the brighter side:

- Better interpreter startup and sis installation time than in 1.9.0. We'll optimize
this further in the future releases.

Uninstall PyS60 1.9.0 before installing 1.9.1 to get the feel of actual installation time.

- All the Python files in the runtime sis are compiled into .pyc files and
included in a zip file. sys.path is updated with the path of this zip file.
This reduced the interpreter startup time considerably.

- A more generic error message is displayed when trying to load an application
without the PyS60 Dependencies installed.

- Support for building just a <subsystem> is provided. Refer build, build_emu,
build_device help of

- Unlike 1.4.x, a single SDK zip contains both gcce and armv5 link libraries.
Separate SDK zips are provided for 3rdEd, 3rdEdFP1 and 3rdEdFP2.

- The default mode of ensymble py2sis command is changed to 'pycore'. All
scripts which refer to pys60 modules socket and calendar should use the new
names - btsocket and e32calendar to use the S60 functionality in pycore mode.
Also renamed "Prioritize PyS60 module library" to "1.4.x compatibility mode"
on the UI of application packager.

Corrected defects:

3230: Problems with applications packaged with console profile and PyS60 mode.
3317: N70 is included in the supported device list in the Getting Started Guide,
even though it's a 2ndEdFP2 device

Here are some of the things that are worse in 1.9.1 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.

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 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.

Feature Requests:
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.2.

Happy hacking!

-- Python for S60 team