>> With this new implementation, you will know when you are using the >> function in a wrong way, >> and this can help you solve some mysterious problems faster. >> >> On other hand, this can be a problem because the current programs, >> which already handle this, could stop working.
As a newbie, here's my take on things. I think there is always a danger if you break backwards compatibility. There is already a lot of PyQT code around and luckily moving it to Pyside is fairly trivial. But, if Pyside starts diverging dramatically from PyQT (and worse, earlier versions of itself), people will be unable to develop on it, because they'll always be wondering if the new release will break what they already have. Pyside is still young so we would expect lots of updates from now. IMHO, breaking backwards compatibility would be a bad idea. I think it would be much better to make the revisions (which certainly seem very useful) some kind of option or module import. Then, we have the option to turn the warnings on or off. _______________________________________________ PySide mailing list [email protected] http://lists.pyside.org/listinfo/pyside
