Re: [PyKDE] Static compilation of PyQt

2006-03-03 Thread Phil Thompson
On Thursday 02 March 2006 11:31 am, Giovanni Bajo wrote: Hello, For the past few months, I have been using a statically-compiled version of PyQt. Statically here means that it's still an external module (.pyd) but it does not depend on the external C++ Qt DLL: the module is totally

Re: [PyKDE] Static compilation of PyQt

2006-03-03 Thread Gerard Vermeulen
On Fri, 3 Mar 2006 08:57:50 + Phil Thompson [EMAIL PROTECTED] wrote: On Thursday 02 March 2006 11:31 am, Giovanni Bajo wrote: Hello, For the past few months, I have been using a statically-compiled version of PyQt. Statically here means that it's still an external module (.pyd) but

Re: [PyKDE] Static compilation of PyQt

2006-03-03 Thread Phil Thompson
On Friday 03 March 2006 9:39 am, Gerard Vermeulen wrote: On Fri, 3 Mar 2006 08:57:50 + Phil Thompson [EMAIL PROTECTED] wrote: On Thursday 02 March 2006 11:31 am, Giovanni Bajo wrote: Hello, For the past few months, I have been using a statically-compiled version of PyQt.

Re: [PyKDE] Static compilation of PyQt

2006-03-03 Thread Jeremy Sanders
On Fri, 3 Mar 2006, Phil Thompson wrote: 1. Changing the API isn't acceptable, import qttable must continue to work. Couldn't this simply be achieved by adding a qttable.py which does from qt import * ? Jeremy -- Jeremy Sanders [EMAIL PROTECTED] http://www.jeremysanders.net/

Re: [PyKDE] Static compilation of PyQt

2006-03-03 Thread Phil Thompson
On Friday 03 March 2006 10:33 am, Jeremy Sanders wrote: On Fri, 3 Mar 2006, Phil Thompson wrote: 1. Changing the API isn't acceptable, import qttable must continue to work. Couldn't this simply be achieved by adding a qttable.py which does from qt import * ? Not if the intention is to

Re: [PyKDE] Static compilation of PyQt

2006-03-03 Thread Giovanni Bajo
Phil Thompson [EMAIL PROTECTED] wrote: 1. Changing the API isn't acceptable, import qttable must continue to work. I tried adding qttable.py which simply contained from qt import *. I found out that the main breakage still happens because, since qt contains all the symbols, people just import

Re: [PyKDE] Static compilation of PyQt

2006-03-03 Thread Phil Thompson
On Friday 03 March 2006 11:15 am, Giovanni Bajo wrote: Phil Thompson [EMAIL PROTECTED] wrote: 1. Changing the API isn't acceptable, import qttable must continue to work. I tried adding qttable.py which simply contained from qt import *. I found out that the main breakage still happens

[PyKDE] Static compilation of PyQt

2006-03-02 Thread Giovanni Bajo
Hello, For the past few months, I have been using a statically-compiled version of PyQt. Statically here means that it's still an external module (.pyd) but it does not depend on the external C++ Qt DLL: the module is totally self-contained. This bring several advantages: - Size. A static