--- Thomas Heller <[EMAIL PROTECTED]> wrote:
>
> I've lost the original email, butI hope this is still on topic:
>
> Now that ctypes works on WindowsCE, someone should revive the venster
> project!
>
> http://venster.sourceforge.net/htdocs/
>
Very cool project, I've been thinking for a while
Ed Blake wrote:
> --- "Michael Foord" <[EMAIL PROTECTED]> wrote:
>
>> You ought to check out Wax. It's a friendly Pythonic layer that sits
>> atop of wx and IMHO is just as easy to use as Tkinter.
>
> Lol! I've been using/tinkering with firedrop for a few weeks now so I am
> vaguely familier wit
--- "Michael Foord" <[EMAIL PROTECTED]> wrote:
> You ought to check out Wax. It's a friendly Pythonic layer that sits
> atop of wx and IMHO is just as easy to use as Tkinter.
Lol! I've been using/tinkering with firedrop for a few weeks now so I am
vaguely familier with wax. I don't really like
The normal .py association on Windows is done with a couple of registry
values:
1. Create a key: HKEY_CLASSES_ROOT\.py
2. Set the default value of this key to: Python.File
3. Create a key: HKEY_CLASSES_ROOT\Python.File\shell\open\command
4. Set the default value to: "C:\Python24\python.exe" "%1"
- Original Message -
From: "Jeffrey Barish" <[EMAIL PROTECTED]>
To:
Sent: Friday, February 24, 2006 11:08 AM
Subject: [PythonCE] Running Python program without getting Python CE window
> Whenever I run a Python application, I get a window titled "Python CE"
> that
> seems to capture s
I'm not sure how to fix your problem though. AFAIK I always thought that
the #! /usr/bin/env pythonw was for use by the shell on unix systems to
determine what interpreter to use. I don't think that is a platform
independent function. Perhaps there is some functionality where you can
change the ou
