You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only thing to keep in mind is that for conda packages there will be no qtsass (libsass cannot be compiled with VS2008 which is what is required for winpy27) available for windows py27 so all that toolchain will not be available for that specific case.
With pypi there should not be a problem.
They will be able to still use the package normally but no custom palette creation at runtime.
Since py27 is going to die soon, I think that there is no problems. As well as py34 will too. Things after py36 are much better for qt things as we can simple install pyqt/pyside from pypi. Actually, I was propose to us to keep some dates/versions of compatible python distribution. Many things we can't do with py27.
In my opinion, we should move some files:
Because they are required if you want to generate the files by yourself up to compiled.
And these ones, if wanted to check a standard example window.
Also, should we provide the 'example' to run the ui_style_edition.
@ColinDuquesnoy @goanpeca opinions?
The text was updated successfully, but these errors were encountered: