[jplauril]

The fast builds use an experimental trick to get more speed out of the interpreter. We are not sure if it will cause compatibility problems or not, but since the performance gain is so significant, it would be great if we could use it in a mainstream release.

If you find out any code that works on the normal build but fails on the fast build, please, please, _please_ report that!

[Michal Sourek]

Hello jplauril & al,
besides other reasons to move from 1.0 to 1.1.6
I was interested to see the announced performance boost

Fortunately
after Bluetooth delivery of the proper Fast.SIS (1.1.6 alpha),
though the installations went as posted in the <About_Fast_SIS.txt>,
the PYTHON has never loaded/started

Series 60 [6670 + 64MB MMC]
Fast.SIS Installation was directed onto MMC Card [24 MB free]

also note:
The (std).SIS installation onto mobile's memory went well and Symbian OS has loaded the PYTHON

Best regards
Michal

[canopus961]

Hi Michal

I have installed fast and normal versions some times, and that problem happened to me in one ocassion.

I think it occurs when you install 1.1.6-fast over 1.1.6-standard. I uninstalled python for s60 and then re-installed 1.1.6-fast, and now it's ok.

Perhaps a full uninstall is needed to have a good re-install.

Greetings.

[otsov]

Originally Posted by canopus961

I think it occurs when you install 1.1.6-fast over 1.1.6-standard. I uninstalled python for s60 and then re-installed 1.1.6-fast, and now it's ok.

Yes, this might be the solution, see release notes for more information:

"
- Reinstallation of 'Python for Series 60' has been noted to be sometimes
problematic on a 7610 phone, if you are installing the same version again (e.g.
overwriting 1.0 with 1.0). To avoid problems with reinstallation, uninstall
Python for Series 60 before installing the software again. (ref: 0031)
"

This is probably due to the underlying installer.

[Michal Sourek]

Hi Canopus,
thx for a note.
My trial was different >>> first to load 1.1.6 Fast.SIS over preious 1.0.1, which was used before my attempt to move ahead.

Once Fast.SIS did proceed through installer but did not launch/execute (silent at all)
I stepped back to load <std>.SIS [to have at least some Python back in work]

However,
my homework is to read the Uninstaller notes in DOCs.

I shall let you know afterwards.

Best regards
M.

[pimol]

Originally Posted by jplauril

...........
If you find out any code that works on the normal build but fails on the fast build, please, please, _please_ report that!

I've installed the fast build only, since it appears. I didn't catch any error (but the ones I already know). I'm using 1.1.6 fast in the device, and 1.1.5 standard in emulator (the 1.1.6 SDK have some installation problem, due to my Java).

Pietro

[Michal Sourek]

Dear members, thx for advice. PDF manual did not bring any bright news, however, removes/installs turned out to Fast.SIS now works well.
I have no idea why, but Fast.SIS 1.1.6 is in-place, up-and-running.
THX again for your interest and help.
Michal

[jplauril]

The reason was that you didn't remove the old SIS before installing the fast version. In-place upgrades are _not_ supported.

[simo.salminen]

Is this reinstallation problem caused by this?

"Reinstallation problem in early SW builds on devices compliant with Series 60 Platform 2nd Edition, Feature Pack 1", KIS000192

If so, there is a workaround (see technical library for more info).

[otsov]

Originally Posted by simo.salminen

Is this reinstallation problem caused by this?

"Reinstallation problem in early SW builds on devices compliant with Series 60 Platform 2nd Edition, Feature Pack 1", KIS000192

If so, there is a workaround (see technical library for more info).

Currently we have the ".pkg"-file organized like suggested in the solution, although there is one extra line prior the embedded packages (if this is the problem then the solution suggestion in the Nokia technical library is wrong). Thanks for pointing this out, filed as #0236.

[bacademy]

Originally Posted by jplauril

The fast builds use an experimental trick to get more speed out of the interpreter. We are not sure if it will cause compatibility problems or not, but since the performance gain is so significant, it would be great if we could use it in a mainstream release.

I wonder what the "experiment trick" is to make it so much faster? Would it benefit Python as a whole, or is it Symbian/ARM specific?

Any reason to hope that we'll get to see the source code of Nokia python / diffs to standard release?

I've often used standard Python source as a learning tool to learn things like threading / sockets for different platforms. The more people know Symbian API's, the better for Nokia I'd imagine.


/bacademy

http://mobile.bacademy.com/

[jplauril]

The trick is Symbian specific and not applicable to other platforms. It's using a little known feature of Symbian that allows you to have writable static data in your DLL's to speed up access to globals. Since no problems have been reported regarding it, this will actually be the default starting from the 1.2 release.

[znakharenko]

Can I get fast Python for S60? Where is download?

[jplauril]

The fast build is the default from version 1.2 onwards, since no incompatibilities were reported.