Recent changes to patches

PythonCE 2.5 for WM Smartphone

2007-09-05T17:39:07Z

Today I compiled a version of PythonCE that runs and installs on WM 5 and 6. Here it is.

Smartphone support

2007-03-24T12:40:28Z

The attached patch provides initial support for running PythonCE on windows mobile powered smartphone devices. The same CAB file will now install and operator on both Pocket PC and Smartphone devices.

The changes are as follows:

1) Altered the cab file inf file to remove potential warnings during installation about incompatible screen sizes.

2) Altered window creation code such that failure to query the size of the Software Input Panel (SIP) is not considered a fatal error. Smartphones do not have SIPs, so SIP related API calls will always return error codes.

3) Sent a couple of smartphone specific window messages to the main edit control. These messages override the behaviour of the '1' key on a cellphone's keypad when in mutli-tap mode such that the user has easy access to symbols such as ()[]@: etc as often needed when entering Python source code. On Pocket PC powered devices these additional messages will be ignored.

4) Fixed a race condition which appeared to be falling over more often than it does on the pocket pc platform. When the second thread within python.exe is started up the main thread suspends itself (via a call to SuspendThread) until it is woken up by the second thread after it has performed initialisation (via a call to ResumeThread).

The issue is if the newly created thread manages to execute it's call to ResumeThread before the main thread has gained control of the processor again after creating the new thread. This leads to the situation of the main thread entering it's call to SuspendThread and never being woken up (due to the second thread having called ResumeThread before we suspended).

The solution I have used is to utilise a named event instead. The main thread creates an event called "PythonStartup", the newly created thread simply sets this event to the signaled state when completed, and the main thread waits for it to be become signaled. This means the main thread can detect when the second thread has completed initalisation even if it completes before we wait for it to occur on the main thread.

Icons for python related file types

2007-03-24T11:32:28Z

The attached patch adds three additional icon resources to the python.exe executable. The patch also contains additional registry settings to associate these icon resources with files of type *.py, *.pyc and *.pyw.

The icons provided in the patch are based on the standard Windows port of Python. They could be replaced if this is deemed to be an issue.

This helps with windows mobile's file explorer hiding file extensions etc by uniquly identifiying to the user which files in a directory listing are python scripts.

Fixing raw_input()

2006-10-06T00:44:46Z

Patches: raw_input() {marked with: //!!}

$src\Python\bltinmodule.c ...replace
builtin_raw_input()
$src\PC\dl_nt.c ...add RawInputChar() for popup dialog

dst flag in localtime

2006-05-23T07:46:51Z

Changes made to wince-compatibility.c to enable
tm_isdst flag.

513a515,518
>
> TIME_ZONE_INFORMATION tzinfo;
> int nIsdst = (GetTimeZoneInformation(&tzinfo)
==TIME_ZONE_ID_DAYLIGHT)?1:0;
>
536a542,544
>
>
>
544c552,556
< tm.tm_yday = Day_Of_Year_By_Month[tm.tm_mon]
+ tm.tm_mday - 1;
---
> tm.tm_yday = Day_Of_Year_By_Month[tm.tm_mon]
+ tm.tm_mday - 1;
> tm.tm_isdst = nIsdst;
>

Patched Makefile for pyexpat and mxDateTime

2005-05-30T23:52:54Z

I patched the makefile to allow mxDateTime and pyexpat
to build.

For mxDateTime an additional patch is needed: You have
to change the following array to a fixed size (f.e. 15):

staticforward PyMethodDef mxDateTime_Methods[];
-->
staticforward PyMethodDef mxDateTime_Methods[15];