Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Hey We'd love to start using graph editor redux but the dependency on sip "api 2" currently means we can't. We have alot of other PyQt4 software loaded (including multiple 3rd-party packages) that expect "api 1", and I'm not sure theres a way to support both simultaneously.
No there isn't a way to support both at the same time. API 2 has been out for quite a while. API1 is no longer supported by PyQt in the next version and isn't supported at all in PySide. You should encourage all developers to upgrade their plugins.
Next version as in python 3? I'll definitely be encouraging developers to write api-agnostic code so it'll work with either - it's just that migrating everything will be a bit too big an undertaking at the moment! ( as well as chasing up 3rd-party software developers! )
I can understand the reluctance to support a backwards compatible version - you can end up chasing your tail a bit!
Thanks for getting back to me so fast!
No, I meant next version of PyQt - which is PyQt5. It's not really about writing API-agnostic code - since it was a major decision of PyQt to internally change to a more "pythonic" way of doing things. That decision doesn't have to happen again and there will only be one API way of doing things going forward. Supporting 2 APIs means writing double the amount of Qt code.
That being said, I just worked on a conversion project at work where we had to modify all the existing code to work with either API. A bit of searching will also let your developers find 2 options of doing this. We chose to bite the bullet now instead of later. The code will fail with the next version - we chose to get ahead of that.
Phil Sloggett
Comments on this feature request:
rbublitz said almost 12 years ago:
Phil Sloggett said almost 12 years ago:
rbublitz said almost 12 years ago:
rbublitz said almost 12 years ago: