From ryan at ape-x.net Sun Jun 13 03:40:30 2004 From: ryan at ape-x.net (Ryan Northey) Date: Sun Jun 13 03:40:48 2004 Subject: [PythonCE] XML-RPC on python pocket pc Message-ID: <1087112430.20267.21.camel@trintop> Hi there, Ive been trying to get python running on a ipaq 5450, running pocket pc 4.20.1081. Ideally i would like to run twisted on it, but i would be happy for it just run an xml-rpc server, or at least an xml-rpc client. Initially i downloaded the version that is linked from python.org - at murkworks.com. Using this i could get the interpeter to run. However, i was not able to import SimpleXMLRPCServer, and when i tried to run xmlrpc client, i got an import error for _socket. Trying to run twisted also failed - i got either the importerror above, or a nameerror because True/False were not defined. So i then checked the version, and while sys.version reports 2.2+, sys. version_info reports 2.3.0. I then tried to use both the python2.3 from http://fore.validus.com/~kashtan/, and the ones from http://debris.demon.nl/PythonCE-2.3. Both of these gave me 'Python is not a valid application'. With the latter i was not sure where the executables etc were supposed to live, so i experimented a little to no avail. So i have a few questions: - What python version is 2.2+? - Is it possible to use 2.2+ for xml-rpc? - If there are missing libs can i just fetch them from the 2.2 dist? - How would i run a script? - Where should i put the files in the 2.3 version? - Are the 2.3 binaries known to work on the above spec? Thanks in Advance, ryan. From isrgish at fastem.com Sun Jun 13 17:35:31 2004 From: isrgish at fastem.com (Isr Gish) Date: Sun Jun 13 17:36:38 2004 Subject: [PythonCE] XML-RPC on python pocket pc Message-ID: Hi Ryan. -----Original Message----- >From: "Ryan Northey" >Sent: 6/13/04 3:40:30 AM >To: "pythonce@python.org" >Subject: [PythonCE] XML-RPC on python pocket pc > >Hi there, > >Ive been trying to get python running on a ipaq 5450, running pocket pc >4.20.1081. > >Ideally i would like to run twisted on it, but i would be happy for it >just run an xml-rpc server, or at least an xml-rpc client. > >Initially i downloaded the version that is linked from python.org - at >murkworks.com. Using this i could get the interpeter to run. However, i >was not able to import SimpleXMLRPCServer, and when i tried to run >xmlrpc client, i got an import error for _socket. > >Trying to run twisted also failed - i got either the importerror above, >or a nameerror because True/False were not defined. > >So i then checked the version, and while sys.version reports 2.2+, sys. >version_info reports 2.3.0. > >I then tried to use both the python2.3 from >http://fore.validus.com/~kashtan/, and the ones from >http://debris.demon.nl/PythonCE-2.3. > >Both of these gave me 'Python is not a valid application'. With the The python.exe iin this distribution dosn't work. I'm not sure why. I have attached a file that does work, and it works fine with the 2.3 version. >latter i was not sure where the executables etc were supposed to live, >so i experimented a little to no avail. > >So i have a few questions: > >- What python version is 2.2+? >- Is it possible to use 2.2+ for xml-rpc? >- If there are missing libs can i just fetch them from the 2.2 dist? >- How would i run a script? >- Where should i put the files in the 2.3 version? >- Are the 2.3 binaries known to work on the above spec? > >Thanks in Advance, > >ryan. > > > > > > > >_______________________________________________ >PythonCE mailing list >PythonCE@python.org >http://mail.python.org/mailman/listinfo/pythonce From kashtan at Validus.Com Sun Jun 13 18:42:52 2004 From: kashtan at Validus.Com (David L. Kashtan) Date: Sun Jun 13 18:42:55 2004 Subject: [PythonCE] Python 2.3 for CE issues Message-ID: <000001c45197$c2c44250$050310ac@DAVIDSLAPTOP> I am almost ready to release a new version of Python/CE. It is based on 2.3.4 and should be much closer in functionality to the Windows Python 2.3.4 It is built for Pocket PC 2003 -- but if people need a Pocket PC 2002 version I can probabl make that as well. David From johnny at debris.demon.nl Mon Jun 14 04:11:06 2004 From: johnny at debris.demon.nl (Johnny deBris) Date: Mon Jun 14 04:11:16 2004 Subject: [PythonCE] Python 2.3 for CE issues In-Reply-To: <000001c45197$c2c44250$050310ac@DAVIDSLAPTOP> References: <000001c45197$c2c44250$050310ac@DAVIDSLAPTOP> Message-ID: <40CD5D9A.1070802@debris.demon.nl> David L. Kashtan wrote: >I am almost ready to release a new version of Python/CE. >It is based on 2.3.4 and should be much closer in functionality >to the Windows Python 2.3.4 > > > That would be very nice... If you need anything infrastructure-wise let me know, I'm tinking especially about a CVS repository, I think it would make sense to have one also for future development and keeping track of changes etc. (although I also noticed the CE community has not used one yet and so far at least it seems most versions are covered, so even though you guys seem to work less structured than what I'm used to at least stuff seems to happen). >It is built for Pocket PC 2003 -- but if people need a Pocket PC 2002 >version I can probabl make that as well. > > > /me raises finger (but don't worry if it's just for me, I can live with the previous one just fine). Cheers, Guido From bokkenka at yahoo.com Mon Jun 14 15:15:21 2004 From: bokkenka at yahoo.com (Nemo) Date: Mon Jun 14 15:15:26 2004 Subject: [PythonCE] RE: Answers (?) to Some of Ryan's Questions... Message-ID: <20040614191521.49963.qmail@web41212.mail.yahoo.com> > Ive been trying to get python running on a ipaq 5450, > running pocketpc 4.20.1081. > - Are the 2.3 binaries known to work on the above spec? I have a 5550 that I've been trying off-and-on... The interpretor runs, but I'm not much farther than that. I'm using 2.3 from... http://fore.validus.com/~kashtan/ ...and "input() & raw_input() for PPC" from... http://www.murkworks.com/Research/Python/PythonCE/PythonCEWiki /Input_28_29_26Raw_5finput_28_29ForPPC > - How would i run a script? I tried once to associate .py and .pyc to Python, but didn't get anywhere. After reading all the doc pages on the 'net (maybe two), I've finally stumbled upon the execfile() command. From the interpretor, I type in... execfile('/storage card/python/scriptname.py') ...and it executes the script. I just discovered this today, so I'm not yet past the "hello world" phase. I'm actually using a note with my execfile commands, then copy/paste into the interpretor. [ctrl][x,c,v] actually works, which saves a ton of typing on the little keyboard. TTFN, Nemo -- N'rn Wisconsin nemo.ironcountyforest.org From isrgish at fastem.com Tue Jun 15 08:58:45 2004 From: isrgish at fastem.com (Isr Gish) Date: Tue Jun 15 16:12:20 2004 Subject: [PythonCE] Python 2.3 for CE issues Message-ID: Thanks, I'm intrested in it. Isr -----Original Message----- >From: "David L. Kashtan" >Sent: 6/13/04 6:42:52 PM >To: "pythonce@python.org" >Subject: [PythonCE] Python 2.3 for CE issues > >I am almost ready to release a new version of Python/CE. >It is based on 2.3.4 and should be much closer in functionality >to the Windows Python 2.3.4 > >It is built for Pocket PC 2003 -- but if people need a Pocket PC 2002 >version I can probabl make that as well. > >David > > >_______________________________________________ >PythonCE mailing list >PythonCE@python.org >http://mail.python.org/mailman/listinfo/pythonce From isrgish at fastem.com Tue Jun 15 08:58:42 2004 From: isrgish at fastem.com (Isr Gish) Date: Tue Jun 15 16:18:09 2004 Subject: [PythonCE] RE: Answers (?) to Some of Ryan's Questions... Message-ID: Hi Nemo, To associate .py and .pyc files you have to make an entry in the registry like this HKEY_CLASSES_ROOT\.py "Default"="PySource" HKEY_CLASSES_ROOT\.pyc Default=PySource HKEY_CLASSES_ROOT\PySource HKEY_CLASSES_ROOT\PySource\DefaultIcon Default=\\Program Files\\Python\\python.exe, 0 HKEY_CLASSES_ROOT\PySource\shell HKEY_CLASSES_ROOT\PySource\shell\open HKEY_CLASSES_ROOT\PySource\shell\open\command Default= "\Program Files\Python\python.exe" "%1" %* This works fine for me. If you want it in a storage card then replace all the refrences to "Prgram Files" with the full path in the storage card. All the best Isr -----Original Message----- >From: "Nemo" >Sent: 6/14/04 3:15:21 PM >To: "pythonce@python.org" >Subject: [PythonCE] RE: Answers (?) to Some of Ryan's Questions... > >> Ive been trying to get python running on a ipaq 5450, >> running pocketpc 4.20.1081. > >> - Are the 2.3 binaries known to work on the above spec? > >I have a 5550 that I've been trying off-and-on... The interpretor >runs, but I'm not much farther than that. I'm using 2.3 from... > http://fore.validus.com/~kashtan/ >...and "input() & raw_input() for PPC" from... > http://www.murkworks.com/Research/Python/PythonCE/PythonCEWiki > /Input_28_29_26Raw_5finput_28_29ForPPC > >> - How would i run a script? > >I tried once to associate .py and .pyc to Python, but didn't get >anywhere. After reading all the doc pages on the 'net (maybe two), >I've finally stumbled upon the execfile() command. From the >interpretor, I type in... > >execfile('/storage card/python/scriptname.py') > >...and it executes the script. I just discovered this today, so I'm >not yet past the "hello world" phase. I'm actually using a note with >my execfile commands, then copy/paste into the interpretor. >[ctrl][x,c,v] actually works, which saves a ton of typing on the little >keyboard. > >TTFN, > >Nemo -- N'rn Wisconsin > >nemo.ironcountyforest.org > > > > >_______________________________________________ >PythonCE mailing list >PythonCE@python.org >http://mail.python.org/mailman/listinfo/pythonce From kashtan at Validus.Com Sat Jun 19 05:12:42 2004 From: kashtan at Validus.Com (David L. Kashtan) Date: Mon Jun 21 00:31:52 2004 Subject: [PythonCE] Python 2.3.4 for StrongARM Pocket PC 2003 (and 2002) availabie Message-ID: <000001c455dd$9392c7a0$140310ac@DAVIDSLAPTOP> I am just about to submit the sources to be integrated into the official Python development tree. That way Python for Windows/CE will easily track the regular Python development. Got the compatibility with full-blown Windows pretty close, so the difference from the normal Win32 build of Python should be very small. I have been using the core Python interpreter for a pretty big project here and 2.3.4 has been very solid on Pocket PC 2003. I have not had time to test ALL the features of core Python nor most of the "external" modules (like PyWin32). So, I am really interested in feedback on how they are working. This version supports zipimport, so you can have a Python23.zip file in "\Program Files\Python\Lib" and it will find modules in there. I have included one that has ALL the Python library modules in it. Also, this version has the ability to access Python zip libraries that are resources -- in fact python23.dll (the core DLL) has the bare minimum Python libraries to be useful (traceback and such), so things can really work with a minimal configuration. I'd like feedback on what a reasonable minimal set of Python library files would be for inclusion in the python23.dll resources. So, please feel free to go to http://www.validus.com/~kashtan and download it. David From anne.wangnick at t-online.de Sun Jun 20 08:26:29 2004 From: anne.wangnick at t-online.de (Anne Wangnick) Date: Mon Jun 21 01:04:23 2004 Subject: [PythonCE] Python 2.3.4 for CE build issues In-Reply-To: <000001c45197$c2c44250$050310ac@DAVIDSLAPTOP> Message-ID: Hello David, I've retrieved your 2.3.4 source distribution, and am now trying to build it for the emulator. I'm running EVC++ 4.0 SP3 and the 2003 SDK. I'm getting: Building lib ... Building pythoncore ... link.exe @C:\Temp\... LINK : fatal error LNK1104: cannot open file 'LIBC.lib' ... The link settings are /nologo /stack:0x10000,0x1000 /dll /windowsce:emulation /MACHINE:IX86 /out:binaries\X86EMRel\pythoncore\python23.dll /implib:binaries\X86EMRel\pythoncore\python23.lib /pdb:binaries\X86EMRel\pythoncore\python23.pdb binaries\X86EMRel\pythoncore\pythonrun.obj binaries\X86EMRel\pythoncore\python_nt.res binaries\X86EMRel\pythoncore\python23_library.lib I've tried before with EVC++ 3.0 and the 2002 SDK. There I was getting the same error, but complaining about 'OLDNAMES.lib'. Can you help? Thanks, Sebastian Wangnick -----Urspr?ngliche Nachricht----- Von: pythonce-bounces@python.org [mailto:pythonce-bounces@python.org]Im Auftrag von David L. Kashtan Gesendet: Montag, 14. Juni 2004 00:43 An: pythonce@python.org Betreff: [PythonCE] Python 2.3 for CE issues I am almost ready to release a new version of Python/CE. It is based on 2.3.4 and should be much closer in functionality to the Windows Python 2.3.4 It is built for Pocket PC 2003 -- but if people need a Pocket PC 2002 version I can probabl make that as well. David From anne.wangnick at t-online.de Sun Jun 20 12:50:33 2004 From: anne.wangnick at t-online.de (Anne Wangnick) Date: Mon Jun 21 01:08:48 2004 Subject: [PythonCE] Python 2.3.4 for CE build issues In-Reply-To: Message-ID: Hello David, I got a bit further by adding the following linker options: coredll.lib /nodefaultlib:oldnames.lib /nodefaultlib:libc.lib /entry:DllMain I'm now getting: link.exe @C:\Temp\nma02260. Creating library binaries\X86EMRel\pythoncore\python23.lib and object binaries\X86EMRel\pythoncore\python23.exp binaries\X86EMRel\pythoncore\python23.dll : warning LNK4086: entrypoint '_DllMain' is not __stdcall with 12 bytes of arguments; image may not run pythonrun.obj : error LNK2019: unresolved external symbol _exit referenced in function _Py_Exit@4 python23_library.lib(acceler.obj) : error LNK2001: unresolved external symbol _exit python23_library.lib(thread.obj) : error LNK2001: unresolved external symbol _exit pythonrun.obj : error LNK2019: unresolved external symbol __except_list referenced in function _PyOS_CheckStack@0 binaries\X86EMRel\pythoncore\python23.dll : fatal error LNK1120: 2 unresolved externals Why does the linker warn about DllMain not being "__stdcall with 12 bytes of arguments" when dl_nt.c defines it properly as BOOL WINAPI DllMain (HANDLE hInst, ULONG ul_reason_for_call, LPVOID lpReserved)? Any clue where exit is defined? And what is going on with _except_list? Lost in Microsoft space, Sebastian Wangnick -----Urspr?ngliche Nachricht----- Von: Anne Wangnick [mailto:anne.nospam01@wangnick.de] Gesendet: Sonntag, 20. Juni 2004 14:26 An: David L. Kashtan; pythonce@python.org Betreff: Python 2.3.4 for CE build issues Hello David, I've retrieved your 2.3.4 source distribution, and am now trying to build it for the emulator. I'm running EVC++ 4.0 SP3 and the 2003 SDK. I'm getting: Building lib ... Building pythoncore ... link.exe @C:\Temp\... LINK : fatal error LNK1104: cannot open file 'LIBC.lib' ... The link settings are /nologo /stack:0x10000,0x1000 /dll /windowsce:emulation /MACHINE:IX86 /out:binaries\X86EMRel\pythoncore\python23.dll /implib:binaries\X86EMRel\pythoncore\python23.lib /pdb:binaries\X86EMRel\pythoncore\python23.pdb binaries\X86EMRel\pythoncore\pythonrun.obj binaries\X86EMRel\pythoncore\python_nt.res binaries\X86EMRel\pythoncore\python23_library.lib I've tried before with EVC++ 3.0 and the 2002 SDK. There I was getting the same error, but complaining about 'OLDNAMES.lib'. Can you help? Thanks, Sebastian Wangnick -----Urspr?ngliche Nachricht----- Von: pythonce-bounces@python.org [mailto:pythonce-bounces@python.org]Im Auftrag von David L. Kashtan Gesendet: Montag, 14. Juni 2004 00:43 An: pythonce@python.org Betreff: [PythonCE] Python 2.3 for CE issues I am almost ready to release a new version of Python/CE. It is based on 2.3.4 and should be much closer in functionality to the Windows Python 2.3.4 It is built for Pocket PC 2003 -- but if people need a Pocket PC 2002 version I can probabl make that as well. David From kashtan at Validus.Com Mon Jun 21 02:14:57 2004 From: kashtan at Validus.Com (David L. Kashtan) Date: Mon Jun 21 02:14:59 2004 Subject: [PythonCE] RE: Python 2.3.4 for CE build issues In-Reply-To: Message-ID: <000001c45757$13c8bb30$140310ac@DAVIDSLAPTOP> That is pretty stunning. In general I am VERY annoyed at the "random" differences between Windows/CE and full-blown Win32. There is no good reason for most of them. Now we see that there are differences between Windows/CE on StrongARM and Windows/CE on x86 emulator! That is just inexcusable! DllMain is indeed correctly define. I have absolutely NO idea why the linker would complain about this when building for x86. There is certainly no problem with this on StrongARM. I'd ignore the warning and see if are any runtime problems. exit() is most definitely defined as a supplied function in Windows/CE. Are you having trouble finding the "C" runtime library? -----Original Message----- From: Anne Wangnick [mailto:anne.wangnick@t-online.de] Sent: Sunday, June 20, 2004 9:51 AM To: David L. Kashtan; pythonce@python.org Subject: Python 2.3.4 for CE build issues Hello David, I got a bit further by adding the following linker options: coredll.lib /nodefaultlib:oldnames.lib /nodefaultlib:libc.lib /entry:DllMain pythonrun.obj : error LNK2019: unresolved external symbol __except_list referenced in function _PyOS_CheckStack@0 binaries\X86EMRel\pythoncore\python23.dll : fatal error LNK1120: 2 unresolved externals From pfalcon at users.sourceforge.net Fri Jun 25 02:15:23 2004 From: pfalcon at users.sourceforge.net (Paul Sokolovsky) Date: Fri Jun 25 02:45:48 2004 Subject: [PythonCE] Python 2.3.4 for StrongARM Pocket PC 2003 (and 2002) availabie Message-ID: <132918510.20040625091523@ua.fm> Hello David, Saturday, June 19, 2004, 12:12:42 PM, you wrote: DLK> I am just about to submit the sources to be integrated into the DLK> official Python development tree. That way Python for Windows/CE DLK> will easily track the regular Python development. Thank you very much! DLK> Got the compatibility DLK> with full-blown Windows pretty close, so the difference from the DLK> normal Win32 build of Python should be very small. The news are very nice! But first of all, does it support notion of current directory? YMMV, but IMHO without this ground feature it's too early to speak of compatibility. Lots of software won't work or will work incorrectly. DLK> I have been using the core Python interpreter for a pretty big project DLK> here and 2.3.4 has been very solid on Pocket PC 2003. I have not had DLK> time to test ALL the features of core Python nor most of the "external" DLK> modules (like PyWin32). So, I am really interested in feedback on DLK> how they are working. What about Python testsuite? I used to hack your previous port by rebuilding it with CELIB (sane C runtine for wince) and running testsuite. Well, I cannot say I made it run fully, but I made around a dozen fixes for some tests to pass. Unfortunately, I paused working on that for now, and if I'd restart that, I would probably say bye to eVC and used arm-wince-gcc port ( http://mamaich.kasone.ru/fr_pocket.htm ). [] -- Best regards, Paul mailto:pfalcon@users.sourceforge.net From kashtan at Validus.Com Tue Jun 29 01:41:23 2004 From: kashtan at Validus.Com (David L. Kashtan) Date: Tue Jun 29 01:41:20 2004 Subject: [PythonCE] Python 2.3.4 regression tests In-Reply-To: <18369763394.20040624094916@ua.fm> Message-ID: <000001c45d9b$b63299a0$180310ac@DAVIDSLAPTOP> I have been working on getting all the Python 2.3.4 regression tests running without making any changes to the tests. Here is what I have found so far (I'm about 1/2 way through the tests). Later this week (or early next week) I will post an update to the Pocket PC Python 2.3.4 distribution with the fixes in it. As you can see, this is going along quite well. David Fixes ----- 1) Need to setup test environment: 1) Extract strings.pyc from .zip & put .zip at end of sys.path This is because zipimport can't do reload() 2) Substitute our own _get_original_stdout() in test.test_support to deal with the PCCESHELL not being a real file. This is needed to correctly trigger a print recursion exception. 3) Change platform name during test run from "PocketPC" to "wince". test_dircache needs the platform to start with "win" to work. 2) Fixed floating point overflow detection 3) Fixed compilation of PC\WinCE\strftime.c to stop infinite recursion 4) Increased stack size to 0x48000 5) Define USE_RECURSION_LIMIT=3000 to force a reasonable recursion limit on the Pocket PC. The Win32 trick of using alloca() to throw a stack allocation exception in order to detect stack overflow doesn't work. 6) Add remove() as synonym for unlink() in cemodule (for module os) 7) Implement more of working directory (convert relative paths to absolute paths) 8) Define strtol to be PyOS_strtol (for cPickle) so integer overflow is detected 9) The mktime() implementation was missing the conversion from localtime to GMT The ctime() implementation was missing the conversion from GMT to localtime The asctime() implementation had some formatting problems 10) Make __stdout__ and __stderr__ point to our output window. 11) Return an empty list when os.listdir() finds an empty directory (instead of an error) Failed tests (still to be fixed) -------------------------------- test test_filecmp test test_fileinput test_format test test_gettext test_glob test_httplib test_imaplib test_import test_importhooks test_locale test_longexp crashed test_mailbox test_mimetools test_minidom skipped -- No module named pyexpat test_mmap test_mpz Failed tests (fixes deferred) ---------------------------- test__all__ - failed in tempfile.py no O_RDWR (because no os support for "os.open") test_MimeWriter - failed in tempfile.py no O_RDWR (because no os support for "os.open") test_atexit - no popen