On 08.09.2010 16:26, ext Darren Dale wrote:
What is the value of calling it Property instead of pyqtProperty?
When discussing PSEP 100, the general agreement was that since we're not aiming for a PyQt clone but an independent and (I hope) better binding (while still highly valuing compatiblity), we shouldn't mimic every questionable PyQt feature blindly. Here, in particular, carrying the name in a specific implementation in the function names (pyqtSignal & pyqtSlot) was found unnecessary. The Property PSEP draft follows the convention created in PSEP 100.
As for keeping the compatibility, if anyone could contribute a compatibility module (or document suitable boilerplate code) to map the incompatibilities between PySide and PyQt, that would be an absolutely great contribution!
Have you considered supporting the property decorator syntax introduced in python-2.6? From http://docs.python.org/whatsnew/2.6.html :
Not really, but that doesn't mean it wouldn't be a great idea! Personally, I just hadn't thought of it. Probably reasonably simple to implement, too, and wouldn't break anything, so would be a good candidate for 1.x content. Thanks for the hint!
A PSEP would need to be written for it (would rather keep it separate from the current draft). I've added it on my todo list but if you want to rush it, check the instructions at [1] and the template at [2] and go for it!
[1] http://www.pyside.org/docs/pseps/psep-0001.html [2] http://www.pyside.org/docs/pseps/psep-0012.html Cheers, ma. _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
