Re: [PyKDE] Deployment on Windows? license compatible

2005-12-07 Thread Ulrich Berning
Michael Zimmermann schrieb: Well, after a bit of trial and error I understand the bit about building a signed interpreter (Actually, this is working as I want it to work). Currently I use my default installation that has QT and PyQT installed. With this setup anyone would be able to use the

Re: [PyKDE] Deployment on Windows? license compatible

2005-12-07 Thread Giovanni Bajo
Ulrich Berning [EMAIL PROTECTED] wrote: What I think about doing is: - Compile the pyQT modules statically into python Why do you want to do that? By protecting PyQt from beeing used by a generic interpreter, there is no need to build PyQt statically linked into Python. One advantage is

Re: [PyKDE] Deployment on Windows? license compatible

2005-12-07 Thread Michael Zimmermann
Ulli, thank you very much for this exhaustive answer. Coming from the world of linux and open-source sometimes I find it difficult to wrap my head around the concepts of licensing issues and code protection! If you think, you miss something in the documentation of VendorID (I'm sure you

Re: [PyKDE] Deployment on Windows? license compatible

2005-12-06 Thread Michael Zimmermann
Ulrich Berning wrote: Hi Ulrich, after being busy with other issues on my dsks for some weeks it is time to come back to our deployment issue on Windows... Sorry, for bothering you again :-) Compiling the pyqt modules statically into a python interpreter results in a generic interpreter,

Re: [PyKDE] Deployment on Windows? license compatible

2005-11-19 Thread Michael Zimmermann
Hi Uli, Compiling the pyqt modules statically into a python interpreter results in a generic interpreter, that can run any python script. This interpreter still violates Trolltech's commercial license agreement. The idea of the VendorID package is to create a specialized interpreter binary

[PyKDE] Deployment on Windows? license compatible

2005-11-18 Thread Michael Zimmermann
Hi there, currently we use pyQT for a research project. In this project we use python, pyqt and qt to generate applications on the client side of a client-server architecture. Basically, two different types of clients can be distinguished: - standalone clients - clients that are controlled

Re: [PyKDE] Deployment on Windows? license compatible

2005-11-18 Thread Ulrich Berning
Michael Zimmermann schrieb: Hi there, currently we use pyQT for a research project. In this project we use python, pyqt and qt to generate applications on the client side of a client-server architecture. Basically, two different types of clients can be distinguished: - standalone clients -

Re: [PyKDE] Deployment on Windows? license compatible

2005-11-18 Thread Michael Zimmermann
Hi Uli, Take a look at the VendorID package (www.riverbankcomputing.co.uk/vendorid). This may be exactly what you are searching for. yes and no :-() If I read the information on the website correctly, I can restrict the import of modules to certain executable files (how to do this for our

Re: [PyKDE] Deployment on Windows? license compatible

2005-11-18 Thread Patrick Stinson
On Nov 18, 2005, at 7:14 AM, Michael Zimmermann wrote: Hi Uli, Take a look at the VendorID package (www.riverbankcomputing.co.uk/vendorid). This may be exactly what you are searching for. yes and no :-() If I read the information on the website correctly, I can restrict the import of

Re: [PyKDE] Deployment on Windows? license compatible

2005-11-18 Thread Ulrich Berning
Michael Zimmermann schrieb: Hi Uli, Take a look at the VendorID package (www.riverbankcomputing.co.uk/vendorid). This may be exactly what you are searching for. yes and no :-() If I read the information on the website correctly, I can restrict the import of modules to certain