Re: [PythonCE] PyCrypto binaries
Matt S. wrote: > > since I've not yet noticed the wxPython and ctypes binaries available > for 2.5). > ctypes seems to be part of the build... Works for me on 2.5 at least. ;) Cheers, Guido ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] PyCrypto binaries
Johnny deBris <[EMAIL PROTECTED]> a écrit : > Matt S. wrote: >> >> since I've not yet noticed the wxPython and ctypes binaries available >> for 2.5). >> > > ctypes seems to be part of the build... Works for me on 2.5 at least. ;) > > Cheers, > > Guido > > Yes, ctypes is now a part of Python standard library thanks to Thomas Heller. As for wxPython, I maybe gonna look in compiling it for 2.5. Although I was disappointed by the difficulty to run it due to the large memory footprint (which is perfectly understandable if you think that the swig bindings are a python layer over a c++ layer which is in turn a layer over a c++ library that wraps GUI native calls) a lot of people seems to use it on the list and I do love the wxPython desktop version, so i'll see if the compilation goes easy ... Besides, any tricks on reducing the memory usage is welcome ;) Regards, Alexandre ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] PyCrypto binaries
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> a écrit : > [EMAIL PROTECTED] wrote: >> Johnny deBris <[EMAIL PROTECTED]> a écrit : >> >> >>> Matt S. wrote: >>> since I've not yet noticed the wxPython and ctypes binaries available for 2.5). >>> ctypes seems to be part of the build... Works for me on 2.5 at least. ;) >>> >>> Cheers, >>> >>> Guido >>> >>> >>> >> >> Yes, ctypes is now a part of Python standard library thanks to >> Thomas Heller. >> As for wxPython, I maybe gonna look in compiling it for 2.5. > It would be _REALLY_ cool. http://wxpyce.wikispaces.com/ is a try, but > the binaries do not work for PythonCE 2.5 / wm5/6. > I ever wanted to try following the Build-process-instructions with the > latest sdk's (out of the hope, it will then run under 2.5 / wm5/6) but > I have no x86-machine and no windows. > Using wxwidgets with latest versions of python / wm would be very, very cool! >> >> Regards, >> >> Alexandre >> > Thanks, > > Mirko >> >> ___ >> PythonCE mailing list >> PythonCE@python.org >> http://mail.python.org/mailman/listinfo/pythonce >> Hello Mirko, I will surely compile wxPyCe for 2.5 these days, as many people should be interested in. However, by experience, don't expect to be able to run wx+pycrypto+numpy+whatever c extension at the same time unless you have a very recent WM 6.0 device (it's a known problem of lack of virtual adressing space for dlls, that has been expanded from 32 MB to 1 GB in WM 6.0 kernel). That's the reason why I have ported Venster (and now secretly working on something FAR more pythonic & high level for embedded gui development), and not because I dislike wx or I wanted to reivent the wheel. It'll be cool if PythonCE people could have the choice between portability (TKinter/wx) at the cost of non-native rendering or high memory consumption or something more specific but that delivers native rendering with a small footprint at the cost of learning something new (VensterCE that may be phased out by my new toolkit). My opinion is that splitting backend & frontend of an application helps portability, and rewriting the frontend for an handeld with its small screen size and its own design guidelines should not be a big deal if the toolkit is easy to learn (and better, pythonic), the biggest advantage of the new toolkit over venster. This is only my opinion, and people are, of course, free to see otherwise and choose what they think best for their own development. That's why I will compile wxPyCe for 2.5 and still support ctypes gui toolkit at the same time. Regards, Alexandre. PS : If someone want to give a try, help, give suggestions, or learn more about the new toolkit, I'll be glad to send you my current work with an example application. The reason why I call the new toolkit "new toolkit" is because I've wanted to call it first pycegui, but realized that it was the bindings of CEGUI for pygame ! Reminds me something about Pyro ;) ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] connect via ssh
Hi Rich, Thanks for the idea and for normal applications this might do the trick (and maybe in the future I'll use it too), but the laptop I was talking about is in fact the brains of my mobile robot (Linux based) and I want to develop an Python application for my PDA to control my robot. To get access to my robot I use ssh. But, as mentioned, I prefer to let my PDA application make the ssh-connection with my robot. But thanks for thinking with me and giving the idea! Regards, Marc Rich Cork wrote: > If you want to connect there is a zaTelnetCF2 the will do the trick > > > >>1. ssh server for wince! (Marc Horst) >> >> >> > >> Hi, >> >> I have a PDA with Windows Mobile on it and would like to connect it to >> my laptop via ssh, I searched for a binary for PyCrypt for Windows >> Mobile/WinCE. However, it seems that these are unavailable. I was >> wondering if someone build PyCrypt already for WinCE/Windows Mobile and >> could do me a big favour by sending me the PyCrypt binaries (or send me >> the URL with the location where you found them) ? >> >> > > > > ___ > PythonCE mailing list > PythonCE@python.org > http://mail.python.org/mailman/listinfo/pythonce > -- Marc Horst - [EMAIL PROTECTED] ___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
Re: [PythonCE] PyCrypto binaries
Hi, On 28/07/2007, at 5:05 AM, [EMAIL PROTECTED] wrote: However, by experience, don't expect to be able to run wx+pycrypto+numpy+whatever c extension at the same time unless you have a very recent WM 6.0 device (it's a known problem of lack of virtual adressing space for dlls, that has been expanded from 32 MB to 1 GB in WM 6.0 kernel). Be very careful here. Windows Mobile 6 devices still have the same 32MB process limit, as Windows Mobile 5.0 (or earlier) devices had. The expanded addressing space is a feature of the Windows Embedded CE 6.0 kernel. But Windows Mobile 6 devices are still using a Windows CE 5.0 based OS kernel (v5.02 to be precise, compared to v5.01 which was used for Windows Mobile 5.0). Some features have been back ported into WinCE 5.02 from WinCE 6.0, but most of the major architectural differences still stand. You will have to wait until Windows Mobile 7 (or whatever the next version is marketed as) for the Windows CE 6.0 kernel features to become available within Windows Mobile devices. For a more complete explination see the blog posting titled "Is Windows Mobile 6 powered by Windows Embedded CE 6.0?" on my blog at http://www.christec.co.nz/blog/archives/18. Hope it helps, Christopher Fairbairn___ PythonCE mailing list PythonCE@python.org http://mail.python.org/mailman/listinfo/pythonce
