Adverti horiz upsell

Graph Editor Redux, Digital Pose Test, MayaStylin' 3.0.0 for Maya (maya script)

cgJedi Animation Suite

Button download


  • 2018, 2017, 2016, 2015, 2014, 2013, 2012

Operating Systems

  • Linux
  • Mac
  • Windows


Last Modified:08/27/2017
File Size: 11.9 MB

Feature Request

A version which uses "SIP api 1"

Submitted by:Phil Sloggett Phil Sloggett
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.

Comments on this feature request:

  • rbublitz

    rbublitz said about 9 years ago:

    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.
  • Phil Sloggett

    Phil Sloggett said about 9 years ago:

    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!
  • rbublitz

    rbublitz said about 9 years ago:

    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.
  • rbublitz

    rbublitz said about 9 years ago:

    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.

Post a comment: