2012/1/5 jelle feringa <jelleferi...@gmail.com>
> No. pythonocc has moved from GPL to LGPL after a long discussion and after
>> balancing pros and cons. It won't move back to GPL again and will remain
>> distributed under the LGPLv3. I don't want to change the license every year.
>>
>
> +1
> GPL is much in demise anyways, the world is moving on...
>
>
>> The PyQt code is about 200lines, that is to say a very small part of
>> pythonocc. A move to PySide is the best solution according to the licensing
>> issue.
>>
>
> Here's a compromise possible:
>
> try:
> from PyQt4 import Qt [ etc... ]
> PYSIDE = False
> except ImportError:
> try:
> from Pyside import Qt [ etc.. ]
> PYSIDE = True
> except ImportError:
> if not PYSIDE:
> # fine, we got pyqt4
> else:
> raise ImportError('neither PyQt4 nor Pyside is installed...
> I'm giving up....')
>
> Its entirely possible to do this...
> The api's are really similar...
>
> Anyway, I find the discussion a little overstaded; man up and supply a
> patch, a little creativity won't kill you ;)
>
> -jelle
>
>
In terms of licensing, the problem is not using the program but
distributing it. In other words, comply with the PyQt license (GPL) is
the responsibility of the developer/manager, not the user. The issue is
then to *remove* any python code based upon PyQt from pythonocc.
Thomas
_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users
