Re: [PyQt] PyQt Licensing Issue
On 12/9/2009 9:49 PM, Hans-Peter Jansen wrote: Giovanni, am I correct, that pyinstaller can be used for packaging commercial apps as well? Yes, you are correct. PyInstaller does not impose any restriction on the license of the executable being built. So it can freely be used to package commercial proprietary applications. -- Giovanni Bajo Develer S.r.l. http://www.develer.com ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
Your confusion is understandable, especially with the recent Qt licensing changes made by Nokia. However, the licensing changes make it much less expensive to use PyQt to produce proprietary applications. The key thing to understand is that you need a separate license for each tool in your development stack. The Qt and PyQt licenses are different. Qt is released under the LGPL. You therefore only need to release your changes to the Qt source code itself. If you want to keep those changes proprietary, you need a commercial license. PyQt is released under the GPL. You therefore need to release all code you build using PyQt unless you purchase a commercial license. I previously had to avoid PyQt on client projects because of the costs of the PyQt + Qt development stack. However, I think the cost of PyQt alone is pretty reasonable. I'm redirecting this email back to the list so that someone will hopefully correct any errors I make in this explanation. Good luck, Richard On Wed 9 December 2009 05:58:47 Prashant Saxena animator...@yahoo.com wrote: Buying a commercial PyQt license is not a problem. But if in any case I would be needing files(.dll or .lib) from Qt SDK then I am sure I have to buy Qt's commercial license also and that would be too costly. Right now I haven't done any test but I'll compile some application modules(.py) using (gcc+cython) for code protection as well as speed gains. I don't if in this case PyQt's (.dll or .lib) files would do the job or I would be needing Qt's files also. I do have a bit of confusion here. Prashant - Original Message From: Richard Esplin richard-li...@esplins.org To: pyqt@riverbankcomputing.com Sent: Wed, 9 December, 2009 12:55:01 PM Subject: Re: [PyQt] PyQt Licensing Issue If you don't want to give away your code, you should buy the commercial license. Richard On Wed 9 December 2009 00:12:45 james infield bimba...@gmail.com wrote: Hello, That might be slightly off topic what do you mean by ...I won't be including the source code... ? Is that your code or PyQt code ? Is there a way to release without giving your code and/or PyQt code ? bimbam snip ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
RE: [PyQt] PyQt Licensing Issue
Sorry to butt in, but from your explanation then as long as you make no changes to the Qt source code itself i.e. you use it as given, and you purchase a PyQt licence you are then able to sell your PyQt-based software? Adriano === Adriano Gagliardi MEng PhD Project Scientist Computational Aerodynamics Aircraft Research Association Ltd. Manton Lane Bedford Tel: 01234 32 4644 E-mail: agaglia...@ara.co.uk Url: www.ara.co.uk -Original Message- From: pyqt-boun...@riverbankcomputing.com [mailto:pyqt-boun...@riverbankcomputing.com] On Behalf Of Richard Esplin Sent: 09 December 2009 15:32 To: pyqt@riverbankcomputing.com Subject: Re: [PyQt] PyQt Licensing Issue Your confusion is understandable, especially with the recent Qt licensing changes made by Nokia. However, the licensing changes make it much less expensive to use PyQt to produce proprietary applications. The key thing to understand is that you need a separate license for each tool in your development stack. The Qt and PyQt licenses are different. Qt is released under the LGPL. You therefore only need to release your changes to the Qt source code itself. If you want to keep those changes proprietary, you need a commercial license. PyQt is released under the GPL. You therefore need to release all code you build using PyQt unless you purchase a commercial license. I previously had to avoid PyQt on client projects because of the costs of the PyQt + Qt development stack. However, I think the cost of PyQt alone is pretty reasonable. I'm redirecting this email back to the list so that someone will hopefully correct any errors I make in this explanation. Good luck, Richard On Wed 9 December 2009 05:58:47 Prashant Saxena animator...@yahoo.com wrote: Buying a commercial PyQt license is not a problem. But if in any case I would be needing files(.dll or .lib) from Qt SDK then I am sure I have to buy Qt's commercial license also and that would be too costly. Right now I haven't done any test but I'll compile some application modules(.py) using (gcc+cython) for code protection as well as speed gains. I don't if in this case PyQt's (.dll or .lib) files would do the job or I would be needing Qt's files also. I do have a bit of confusion here. Prashant - Original Message From: Richard Esplin richard-li...@esplins.org To: pyqt@riverbankcomputing.com Sent: Wed, 9 December, 2009 12:55:01 PM Subject: Re: [PyQt] PyQt Licensing Issue If you don't want to give away your code, you should buy the commercial license. Richard On Wed 9 December 2009 00:12:45 james infield bimba...@gmail.com wrote: Hello, That might be slightly off topic what do you mean by ...I won't be including the source code... ? Is that your code or PyQt code ? Is there a way to release without giving your code and/or PyQt code ? bimbam snip ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt --- This email contains information that is private and confidential and is intended only for the addressee. If you are not the intended recipient please delete it and notify us immediately by e-mailing the sender. Note: All email sent to or from this address may be accessed by someone other than the recipient, for system management and security reasons. Aircraft Research Association Ltd. Registered in England, Registration No 503668 Registered Office: Manton Lane, Bedford MK41 7PF England VAT No GB 196351245 ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
On Wednesday 09 December 2009, 16:49:49 Adriano Gagliardi wrote: Sorry to butt in, but from your explanation then as long as you make no changes to the Qt source code itself i.e. you use it as given, and you purchase a PyQt licence you are then able to sell your PyQt-based software? Yes. Pete ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
On Wednesday 09 December 2009 08:22:25 am Hans-Peter Jansen wrote: On Wednesday 09 December 2009, 16:49:49 Adriano Gagliardi wrote: Sorry to butt in, but from your explanation then as long as you make no changes to the Qt source code itself i.e. you use it as given, and you purchase a PyQt licence you are then able to sell your PyQt-based software? Yes. Pete If I use PyQT to build a free product that can be used to create a commerical product - Do I need to purchase a commerical license or does just the developer creating the commerical product (from my free product)? johnf ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
On Wed, 9 Dec 2009 09:57:40 -0800, John jfabi...@yolo.com wrote: On Wednesday 09 December 2009 08:22:25 am Hans-Peter Jansen wrote: On Wednesday 09 December 2009, 16:49:49 Adriano Gagliardi wrote: Sorry to butt in, but from your explanation then as long as you make no changes to the Qt source code itself i.e. you use it as given, and you purchase a PyQt licence you are then able to sell your PyQt-based software? Yes. Pete If I use PyQT to build a free product that can be used to create a commerical product - Do I need to purchase a commerical license or does just the developer creating the commerical product (from my free product)? The latter. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
Thanks for your kind reply. My application is purely python+PyQt based. I can buy a PyQt commercial license and release the application on all platforms supported by PyQt. Releasing mean the .pyc files plus necessary PyQt files(.lib,.dll,.so etc.) required. AFAIK this would do the job. Correct me If I am wrong. Just now I have finished some tests where I compiled .py files using cython+gcc(pure python mode) on XP 32. All of these .py files has PyQt imports. When I replace .pyc files with .pyd files, application crashes. I am still investigating for the cause but I am not so good in c/c++ stuff. I already posted a new topic about this problem but haven't got any reply so far. Up to here I am not at all touching Qt but if in case this compiling stuff need some thing from Qt in order to make my PyQt app error free, then it would be a problem. Prashant ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/ ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
On Wednesday 09 December 2009, 19:40:25 Prashant Saxena wrote: Thanks for your kind reply. My application is purely python+PyQt based. I can buy a PyQt commercial license and release the application on all platforms supported by PyQt. Releasing mean the .pyc files plus necessary PyQt files(.lib,.dll,.so etc.) required. AFAIK this would do the job. Correct me If I am wrong. You will need to scotch users from becoming developers in some way, that try to resell their stuff. You might want to check the VendorID package, or at least, use pyinstaller to make this abuse hard. This may help for the problem below, too. Phil, do you consider such practice as sufficient? Giovanni, am I correct, that pyinstaller can be used for packaging commercial apps as well? Just now I have finished some tests where I compiled .py files using cython+gcc(pure python mode) on XP 32. All of these .py files has PyQt imports. When I replace .pyc files with .pyd files, application crashes. I am still investigating for the cause but I am not so good in c/c++ stuff. I already posted a new topic about this problem but haven't got any reply so far. Up to here I am not at all touching Qt but if in case this compiling stuff need some thing from Qt in order to make my PyQt app error free, then it would be a problem. Yes, but with a PyQt commercial license, you're always free to fix the problem in the wrapper or in a custom sip binding, don't you? Pete ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
On Wed, 9 Dec 2009 21:49:57 +0100, Hans-Peter Jansen h...@urpla.net wrote: On Wednesday 09 December 2009, 19:40:25 Prashant Saxena wrote: Thanks for your kind reply. My application is purely python+PyQt based. I can buy a PyQt commercial license and release the application on all platforms supported by PyQt. Releasing mean the .pyc files plus necessary PyQt files(.lib,.dll,.so etc.) required. AFAIK this would do the job. Correct me If I am wrong. You will need to scotch users from becoming developers in some way, that try to resell their stuff. You might want to check the VendorID package, or at least, use pyinstaller to make this abuse hard. This may help for the problem below, too. Phil, do you consider such practice as sufficient? It depends - it's all about taking steps that are appropriate to the particular application and user profile. In some cases I'd be happy with a section in the EULA, in other cases I'd want some specific technology in place. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
On Tue, 8 Dec 2009 17:46:20 +0530 (IST), Prashant Saxena animator...@yahoo.com wrote: Hi, I am planning to release the beta version(Testing) of an application written using python+PyQt. I won't be including the source code with the installation. Do I have to purchase the PyQt commercial license now itself or I can purchase before releasing the commercial version. It'll surely take 2-3 months before I reach to final version and releasing the commercial version is purely based on the users opinion and success. You need commercial licenses before you distribute your application to your users for the first time - not when you release the final version. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
On Tue, 08 Dec 2009 12:25:15 +, Phil Thompson p...@riverbankcomputing.com wrote: On Tue, 8 Dec 2009 17:46:20 +0530 (IST), Prashant Saxena animator...@yahoo.com wrote: Hi, I am planning to release the beta version(Testing) of an application written using python+PyQt. I won't be including the source code with the installation. Do I have to purchase the PyQt commercial license now itself or I can purchase before releasing the commercial version. It'll surely take 2-3 months before I reach to final version and releasing the commercial version is purely based on the users opinion and success. You need commercial licenses before you distribute your application to your users for the first time - not when you release the final version. As for Qt, the commercial license explicitly forbids relicensing of existing GPL/LGPL code (even if you own the copyright). So basically Nokia requires that you buy a commercial license at the beginning of development, not at release time. -- Giovanni Bajo Develer S.r.l. http://www.develer.com ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
On Tue, Dec 8, 2009 at 8:14 AM, Giovanni Bajo ra...@develer.com wrote: On Tue, 08 Dec 2009 12:25:15 +, Phil Thompson p...@riverbankcomputing.com wrote: On Tue, 8 Dec 2009 17:46:20 +0530 (IST), Prashant Saxena animator...@yahoo.com wrote: Hi, I am planning to release the beta version(Testing) of an application written using python+PyQt. I won't be including the source code with the installation. Do I have to purchase the PyQt commercial license now itself or I can purchase before releasing the commercial version. It'll surely take 2-3 months before I reach to final version and releasing the commercial version is purely based on the users opinion and success. You need commercial licenses before you distribute your application to your users for the first time - not when you release the final version. As for Qt, the commercial license explicitly forbids relicensing of existing GPL/LGPL code (even if you own the copyright). So basically Nokia requires that you buy a commercial license at the beginning of development, not at release time. Right, see http://qt.nokia.com/products/licensing : You must purchase a Qt Commercial Developer License from us or from one of our authorized resellers before you start developing commercial software. The Qt Commercial Developer License does not allow the incorporation of code developed with the Qt GNU LGPL v. 2.1 or GNU GPL v. 3.0 license versions into a commercial product. Darren ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
On Tuesday 08 December 2009, 13:25:15 Phil Thompson wrote: On Tue, 8 Dec 2009 17:46:20 +0530 (IST), Prashant Saxena animator...@yahoo.com wrote: Hi, I am planning to release the beta version(Testing) of an application written using python+PyQt. I won't be including the source code with the installation. Do I have to purchase the PyQt commercial license now itself or I can purchase before releasing the commercial version. It'll surely take 2-3 months before I reach to final version and releasing the commercial version is purely based on the users opinion and success. You need commercial licenses before you distribute your application to your users for the first time - not when you release the final version. If I understand the PyQt licensing correctly, he should have bought the license before start developing, shouldn't he? Pete ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
On Tue, 8 Dec 2009 14:29:07 +0100, Hans-Peter Jansen h...@urpla.net wrote: On Tuesday 08 December 2009, 13:25:15 Phil Thompson wrote: On Tue, 8 Dec 2009 17:46:20 +0530 (IST), Prashant Saxena animator...@yahoo.com wrote: Hi, I am planning to release the beta version(Testing) of an application written using python+PyQt. I won't be including the source code with the installation. Do I have to purchase the PyQt commercial license now itself or I can purchase before releasing the commercial version. It'll surely take 2-3 months before I reach to final version and releasing the commercial version is purely based on the users opinion and success. You need commercial licenses before you distribute your application to your users for the first time - not when you release the final version. If I understand the PyQt licensing correctly, he should have bought the license before start developing, shouldn't he? No. That used to be the case but with the release of the LGPL Qt I relaxed that condition. Phil ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
Hello, That might be slightly off topic what do you mean by ...I won't be including the source code... ? Is that your code or PyQt code ? Is there a way to release without giving your code and/or PyQt code ? bimbam 2009/12/8 Prashant Saxena animator...@yahoo.com Hi, I am planning to release the beta version(Testing) of an application written using python+PyQt. I won't be including the source code with the installation. Do I have to purchase the PyQt commercial license now itself or I can purchase before releasing the commercial version. It'll surely take 2-3 months before I reach to final version and releasing the commercial version is purely based on the users opinion and success. Prashant The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/ ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] PyQt Licensing Issue
If you don't want to give away your code, you should buy the commercial license. Richard On Wed 9 December 2009 00:12:45 james infield bimba...@gmail.com wrote: Hello, That might be slightly off topic what do you mean by ...I won't be including the source code... ? Is that your code or PyQt code ? Is there a way to release without giving your code and/or PyQt code ? bimbam snip ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
