Qt for Python Development Notes: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
(248 intermediate revisions by 12 users not shown)
Line 1: Line 1:
== 2018 ==  
[[Category:Qt for Python]]
== 2020 ==
==== 2. July 2020 ====


==== 01. March 2018 ====
* Infra Update
- Important things we should discuss:
** Timeouts issues, increasing it is not a solution.
  - PySide2 versioning
** How to proceed with dev to use Qt6
    - Do official releases follow Qt branch names?
*** merge without CI
    - Will we have snapshots, and if so, will they be uploaded to pip? How will we handle snapshot versions?
*** clarify the yaml configuration
    - alpha / beta / RC versioning?
** 5.14.2.3 new release planned
    - Probably need to take into account PEPs for versions pushed to Pypi.
* Selectable Features
    - Shiboken / PySide2 versions in sync?
** snake_case for camelCase names.
    - Will we specify a version for 5.6 branch?
** (in progress) access Qt properties directly:
  - Do we want to deploy msvcrt dlls into Windows packages?
*** For 'label = QLabel("hello")', we could do 'label.text = "bye"' instead of using the 'label.setText("bye")'.
  - How will the pip upload process look like? Manual uploads? Who takes care of it?
* Qt6 compatibility
** QML working on Linux (this will enable us to work on the registration)
* Some improvements in the documentation generation must be done to speed up the process.
* pyside2_config.py file to CMake
** include XConfig.cmake files on the wheel
* sdist package
** nice to have: pip install -e ., but at the moment we have three egg-info directories (error)
* Starting again with the cross compilation of PySide for embedded linux.
==== 25. June 2020 ====


==== 22. February 2018 ====
* Infra update
- dev branch is still/again broken in CI, seems like pyside issues
** Release of the second set of Windows 64bit wheels.
- changes to create automatic snapshots out of CI is still under review
** Issues on the CI due to some internal issues, everything should be running soon.
- Numerous small fixes to the [https://bugreports.qt.io/browse/PYSIDE-363 doc] generation, significantly bringing down the number of documentation warnings
* (in progress) from __future__ import newapi
- Massaged build rules to improve built packages
** it's tricky to provide snake_case instead of camelCase
    - Removed unnecessary _utils.py file [https://bugreports.qt.io/browse/PYSIDE-600 PYSIDE-600]
** issues with tp_getattro
    - Changed wheel package names to contain both PySide2 version and Qt version against which it was built [https://bugreports.qt.io/browse/PYSIDE-613 PYSIDE-613]
** creating modified Python objects to replace the original types at runtime
    - Finally got libclang to be deployed into packages
* (in progress) from __future__ import newproperties
    - Improved build process not to copy unnecessary symlinks and duplicating libraries when creating wheel (so that you don't get 3x size increase because of 3x number of WebEngine libraries) [https://bugreports.qt.io/browse/PYSIDE-495 PYSIDE-495]
** Still many things to go
    - Fixed wheel package names to contain correct minimum deployment target with which macOS was built with (on further analysis, this will need further improvement) [https://bugreports.qt.io/browse/PYSIDE-612 PYSIDE-612]
* PYSIDE-1282 pthread crash solved, and will be merge in 5.14
    - Fixed rpath handling for QtWebEngineProcess when creating standalone packages on macOS [https://bugreports.qt.io/browse/PYSIDE-605 PYSIDE-605]
* Indentation fixes for generated code. Prefix adaptation for a standard format so it can be loaded in QtCreator (from warning and stuff)
- Added CMake build rules for scriptable application example [https://bugreports.qt.io/browse/PYSIDE-597 PYSIDE-597]
* Qt for Python 6 is partially working in some platforms
- Investigated and fixed a heap corruption bug in a test that caused constant crashes on macOS CI runs
** Still many missing modules,
- Reduced number of warnings when running shiboken to create user bindings (like scriptable application example) [https://bugreports.qt.io/browse/PYSIDE-587 PYSIDE-587]
** CMakeLists.txt files needs some love,
- [https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595]: Making slow progress, still debugging. It's a difficult process, but assumption is that it will work.
** Needs to adapt CI for the new dev branch
- Havent's merge [https://codereview.qt-project.org/#/c/220083/ this new patch] because we should be 200% sure it's properly working.
** Windows has some issues still :)
- Working on a few bugs [https://bugreports.qt.io/browse/PYSIDE-106 PYSIDE-106] [https://bugreports.qt.io/browse/PYSIDE-570 PYSIDE-570]
* libclang situation, are we sharing the same version for qdoc, qtcreator, qt, etc...?
- One of the bugs [https://bugreports.qt.io/browse/PYSIDE-611 PYSIDE-611] was valid only for 5.6, but I noticed a strange behaviour on 5.9, so I will keep working on it, even after we move 5.6 to cherry pick mode.
** Need to check in case we decide to update
* Commercial wheels split progress


==== 15. February 2018 ====
==== 18. June 2020 ====
- CI broken, 5.6 & dev branch broken, 5.9 just got working again
- first TP will be 5.11 based (needs 5.11 git branches, 5.6 branch goes into cherry-pick mode, 5.9 branch remains main target)
- more modules added to doc, qt3d & qtquick has some special handling
- snippet work ongoing
- snapshot generation on the agenda
- lots of bug fixing e.g.: [https://bugreports.qt.io/browse/PYSIDE-104 PYSIDE-104]
- [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560]


==== 8. February 2018 ====
* Infra update
- Looking through previous EuroPython talks to write a proposal for this year.        
** The new windows wheels still had some issues, it seems the latest are OK, and we would need to publish '_2' wheels.
- Working on a few bugs (fixed a couple related to objects references),               
** Some issues with macOS builds for 5.15.0
    - that sadly will open new issues with memory management. A further analysis on this matter could improve the current memory leaks on PySide.                          
* Qt6 compatibility
- Trying to "organise" a little the typesystem XML files.                             
** This is stopping the improvements in the QML integration story
- Working on [https://bugreports.qt.io/browse/PYSIDE-104 PYSIDE-104] that ended up being a general issue on PySide about a proper verification between slots and signals arguments, to find the best match.
** We need this merged before continuing https://codereview.qt-project.org/c/qt/qtbase/+/301979
- Merged a few build related changes in 5.6
* Merged a bug fix to 5.12 (the CI was not broken)
  - Pending change for [https://bugreports.qt.io/browse/PYSIDE-593 PYSIDE-593]
* (in progress) Qt6 Properties camelCase to lower_case
  - Pending change for [https://bugreports.qt.io/browse/PYSIDE-605 PYSIDE-605]
** Not a trivial task
  - Merged changes for [https://bugreports.qt.io/browse/PYSIDE-603 PYSIDE-603] and [https://bugreports.qt.io/browse/PYSIDE-604 PYSIDE-604]
** It's possible to rename dynamically functions, and other things.
- Investigated and attached minimal reproducible example for [https://bugreports.qt.io/browse/PYSIDE-585 PYSIDE-585]
** Containers needs to be taken care too
- Investigated some macOS build related aspects for package release
** Having more than one object with the same ID is challenging
- 5.6 CI is unblocked, but 5.9 CI is blocked due to qtbase issues (version bumping)
** Issues with str based objects
- [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560] waiting for view
* Fixed PYSIDE-1332, PYSIDE-1327
- [https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595] work ongoing, not ready yet
* (in progress) Commercial wheel are almost ready on Linux, later some changes for Windows and macOS are required.
- [https://bugreports.qt.io/browse/PYSIDE-363 PYSIDE-363]  Documentation: Fixed images, fix handling of qdocconf files  that contain several modules. Looking at snippet resolution.
* (in progress) WigglyWidget example almost there
- Problems with Qt3D due to refactoring of Qt3Dextras in 5.10. Pushed  [https://codereview.qt-project.org/#/c/219105/ patch] suggestion.
* (in progress) New StyleSheet tutorial.
==== 11. June 2020 ====


==== 1. February 2018 ====
* Infra Update
- Continued work on documentation [https://bugreports.qt.io/browse/PYSIDE-363 PYSIDE-363], fixed static pages, add more modules, fixed parameters to qdoc, images
** MSVC 2019 DLL issue with 5.15.0, we shipped a DLL that was too new. (https://bugreports.qt.io/browse/PYSIDE-1323)
- The GettingStarted wiki is getting better, besides a cleaning it a bit
** A new set of wheels will be available for Windows users (without a modern MSVC)
  - moved the topics around to have guidelines by supported platform (''a la Qt'')
* QEnum implementation
  - have received feedback and trying to add more information
** Waiting for review
- Addressed bugs:
** Qt5 compatible
  - [https://bugreports.qt.io/browse/PYSIDE-34 PYSIDE-34]
** QFlag is also exposed
  - [https://bugreports.qt.io/browse/PYSIDE-264 PYSIDE-264]
* Research: Qt6 Properties camelCase to lower_case
  - cleaning a bit Shiboken's XML files.
** https://bugreports.qt.io/browse/PYSIDE-1019
  - [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560]
* Started to fix missing types information: https://bugreports.qt.io/browse/PYSIDE-1318
    - ported to 5.9, extended to 18 header files
* Fix memory leaks in property accesors (https://bugreports.qt.io/browse/PYSIDE-1321),
    - solved unicode problem
* Fix code generation bugs (https://bugreports.qt.io/browse/PYSIDE-1325)
    - reduced the patches to be minimal (avoid many #ifdef's, use a verbose macro name if possible)
* Incremental wheels
    - made everything compile but one announced file: "object.h" depends on the heaptypes solution ([https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595]). Removed WIP status,review pending.
* Missing pyside2uic features
  - [https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595]
* Backports for 5.12
    - Started experimenting
** Ask Gerrit admins
    - turned out that the signature extension barfed because it could no longer find the type "__name__". The function PyType_Type.tp_new needs to be called to provide the "ht_name" attribute that is used in heaptypes.
** Try one last patch.
- solving the attribution file issues.
- Pending patches to fix libICU issues
- Pending patches to fix OpenSSL issues [https://bugreports.qt.io/browse/PYSIDE-599 PYSIDE-599]
- Pending patches to deploy libclang library for shiboken
- Improved documentation about OpenSSL dependency
- Pending patches for cleaning up build scripts a bit (logging and refactoring)
- Pending patches to reduce barrage of warnings [https://bugreports.qt.io/browse/PYSIDE-587 PYSIDE-587]
- Pending patch for adding CMake build rules for the scriptable_application example (useful as a reference on how to use shiboken for custom bindings) [https://bugreports.qt.io/browse/PYSIDE-597 PYSIDE-597]
- Old 5.6 CI integration issue fix, but a new issue appeared that was fixed for 5.9 and dev, but still blocks 5.6
- Updated the qml basics tutorial


==== 25. January 2018 ====
==== 4. June 2020 ====
- Pyside not renamed
- Releasing preparation
  - pip packages created by coin
  - Automated release testing (RTA) (installing pip, launching an example)
  - final selection of release package targets to be define closer to release (depending on current stable ABI work)
- Investigation doc issues when using prefix & shadow builds
- Need to identify prime demos/examples
- Started to rework [[PySide2 GettingStarted|Getting Started Guide]] wiki
- Addressed cmake build issues
- Handling libICU issues (causing linker issues when importing QtCore)
- Continued work on [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560]
-


==== 18. January 2018 ====
* CI Update
  - macOS framework fix (should ignore qt4 system headers)
** Limited API reports work
  - another patch on top to fix OpenGL integer types on mac / Linux (GLuint64, GLint64)
** Improve integrations on macOS
  - Fixed so that PySide 5.6/5.9 is not linked against the Python shared / static library (this was wrong because the symbols need to be picked up by the dynamic loader from the python interpreter itself). http://bugreports.qt.io/browse/PYSIDE-522
* Documentation updates for Qt Assistant
  - Completed move of examples from pyside-examples.git to pyside-setup
* PYSIDE-1257 cx_Freeze issues seems to be related to cx_Freeze itself.
  - added additional OpenGL2 core example
* Q_ENUM and QFlag will be soon available.
  - fixed testrunner (these silently failed since forever) https://codereview.qt-project.org/#/c/216732/
* New Shiboken example to expose a custom Qt Widget to Python
  - fixed issues whereby wrong QObject ctors were selected
* loadUiType is back into PySide (relies on pyside2-uic on PATH)
  - removed webkit from Pyside2 build 
* Other bug fixes.
  - talk about Windows specific instructions for [[PySide2 GettingStarted|Getting Started Guide]]
  - Qt3D issues in Qt 5.10 fixes
  - clazy warning fixes
  - Stable ABI work (started to convert implementations) (see [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560])
    - requires adoption of HeapTypes
  - QML tutorial updates
  - Doc snapshots being prepared


==== 11. January 2018 ====
==== 28. May 2020 ====
- multi pyside packages (not easy to do)
* Releases
  - unlikely to achieve until TP
** 5.15.0 and 5.14.2.2 were released :) https://www.qt.io/blog/qt-for-python-5.15.0-is-out
  - a package per python release (3.4, 3.5, 3.6, 2.7)  
** Thoughts about 5.14.2.3
  - package per platform (win 32bit|64bit, mac, linux)
** 5.15.1 release is still not defined
  - long term task to convert to reduced Python API (to support multi 3x packages)
* Documentation
  => have to cut some targets: one 3x and 2.7 release
* CI Status
  -> create doc howto to encourage custom builds for not covered platform combo
** The limited-api check was somehow bypass by one specific patch https://codereview.qt-project.org/c/pyside/pyside-setup/+/298845 We need to keep an eye to avoid this in the future.
  -> do we need commercial for release
* Backlog status [https://bugreports.qt.io/secure/RapidBoard.jspa?rapidView=262&view=planning.nodetail&selectedIssue=PYSIDE-463&issueLimit=100 check it here]
- pysinstaller is an installer
* QML Integration update
    -> deployqt tool not necessary
** We are working on finishing the implementation of Q_ENUM, to be able to use the singletonType registration
    -> documentation required stating the option
** Additionally, we are looking into the uncreatableType registration too.
- rename import options
* Development branch for Qt6
  - rename via alias possible
** We need the following before jumping into dev.
  -> still an issue when looking up particular types but probably manageable 
*** QList/QVector
  - renaming option: Qt4Pyton, QtPy, QtPython, Python4Qt, Qt
*** QString -> integrated (clarity)
- example shift
  - https://codereview.qt-project.org/#/c/215900/
- Basics for doc generation toolchain
- Issues where cmake picks up platform Qt references where it should use a Qt custom install
- Qt3D bindings still under progress
- [https://bugreports.qt.io/browse/PYSIDE-34 PYSIDE-34] & [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560]  
- Documentation
  - minor doc fixes
  - documenting examples


==== 4. January 2018 ====
==== 21. May 2020 ====
  - multi pyside packages (not easy to do)
* '''Holiday'''
  - renaming Pyside to "Qt for Python"
    - quite challenging due to implied import and lib changes
    - alias for existing imports would be beneficial
  - discussion around existing function test
    -> working assumption is that we ignore added function and check for existing base line only
    -> effort too large to maintain every single new addition
  - discussed issues around concurrent existing Qt builds while building pyside (potential cross leakage)
  - various fixes to doc generation steps (see [https://bugreports.qt.io/browse/PYSIDE-363 PYSIDE-363])
  - discussed need for good examples as part of documentation
    -> considered options to cleanup and remove need for submodule


== 2017 ==  
==== 14. May 2020 ====


<div class="mw-collapsible mw-collapsed" style="overflow:auto;">
* CI Updates
** CI blocked due to some provisioning issues in red hat
** 5.14.2.2 Release is on hold
** 5.15 commercial release in preparation
** License check
* 5.15 Release
** Pickling changes
** Examples
** loadUiType
* Tutorials rcc, designer
** Add project's tutorial.
* Continue research of using Qt6
* __qualname__ attributes are almost done
** This changes was required for the pickling support.


==== 21. December 2017 ====
==== 7. May 2020 ====
- Issues building for Windows for Python 2 and 3 (on coin)
* CI Updates
- discussing potential pyside demo/example for RTA purposes
** Issues with the provisioning, for example the connection with PyPi, still in progress.
- Continued work on macOS / Qt 4 header issues, progress is there
** We will add a requirements.txt for provisioning.
  - breaks GL signature test on Linux, needs further investigation
* Issues
- Investigated PyInstaller (potential option to deploy apps written with Pyside)
** PYSIDE-1255 Signal not reached in QML
  - seems to work almost out-of-the-box for deploying PySide apps
** Pickling Qt Enums PYSIDE-15
- Investigated building one package compatible with multiple Python 3.x minor versions
*** Almost finished, but we are waiting for PYSIDE-1285 to be fix (modulename, qualname).
  - not possible currently, will require a lot of work, possibly not feasible
** Many other minor bugs have been fixed, but still there are a couple of strange ones.
  => we need to build 3.4,3.5,3.6 * win, linux, mac packages = 9 packages
** First attempts to build shiboken with Qt6
  => 3 more for each platform and Python 2.x
** Ideas repo re-organization
  => commercial packages?
* Features
- lots of discussions and fixing of doc tool chain (qdoc in dev currently broken)
** Commercial addons
  - adding documentation has begun in earnest
** Tutorials
- continued work on PYSIDE-578
*** rcc
*** uic
*** QTranslator (*)
*** ...
** QtAssistant integration
** loadUiType
** The new way of registering QML properties needs to be applied to the code base.


==== 7. December 2017 ====
==== 30. April 2020 ====
- pip wheel installation
* CI Updates
  - adding support for simultaneously python 2 and 3 builds
** Issues with pip upgrades
  - open issues: test installation towards multi python 3 versions
** Planning new Python versions for new configurations.
  - delivery channel for Pyside binaries (pip server? local install from qt account download?)
* Update on bugs still around after 5.14.2.1
- investigate options to have sth like pyinstallqt (pysinstaller is a possibility)
** 1271: Deadlock (fixed)
- final keyword support by shiboken
** 1255: Signal not reached in QML (still in progress)
- Qt3D bindings patch close to completion - > requires some Qt changes in 5.9.4 or later Qt
** 1280: Research
- fixing pyside build issues when encountering Qt 4 headers on macOS
* Features
- PYSIDE-578 (testing procedure/testrunner) -> adds heuristic to adapt to failure rates (flakiness handling)
** QML interaction
  - concerns that running all tests 5 times adds too much load on the CI (test runs needed)
** Q_ENUM and pickling SbkEnum
** Commercial Addons


==== 30. November 2017 ====
==== 23. April 2020 ====
- packaging related coin changes
* 5.14.2.1 Release
- last weeks merges between 5.6 and 5.9+ blocking coin have been fixed (in particular on RHEL)
* New bugs around threading:
  - 5.9 + 5.6 are passing, dev has some private Qt changes which will affect pyside/dev
** https://bugreports.qt.io/browse/PYSIDE-1271
- lots of coin infrastructure issues
** https://bugreports.qt.io/browse/PYSIDE-1255 needs to be reopen.
- RTA test wheels added (install and launch single example)
* Documentation changes around the replacement of the old pysideuic module
- crash bugs in 5.6 branch reported but not details known yet (waiting for more details)
* Q_ENUM update
- some discussion what changes should be put to 5.6 vs 5.9 branch
** How to get a reference from the QMetaObjectBuilder without a QObject based project?
- Qt3D bindings started
* mypy compatibility
  - some changes in qt3d/5.9 required)
** depends a bit on the Q_ENUM
  - shiboken bugs discovered in the process (virtual function guessing & some comparison operators for namespace generated)
- small regression related to rpath handling on Linux
- open pip wheel issues:
  - handling of multi Python version wheels
- testrunner bugs addressed and reducing flakiness
- issues in Pyside when building with gcc 7.x
- qdoc from qt5/dev is required for pyside due to webxml support
  - it is a problem for the pyside/5.9 branch


==== 23. November 2017 ====
==== 16. April 2020 ====
- pip wheel support issues on Linux solved (not yet verified)
  -> libICU usage on Linux should be enabled via pyside setup script
  -> downloaded from qt account download area
  - discussion how to do wheel builds for different Qt base lines -> implies to different wheel packages
  - need to evaluate how different python versions on various Linux distros impact wheel binaries
  - target: 6 wheels (2 per platform for 2.7 & 3.5+ Python)
  - OpenGL example
  - merge 5.6-> 5.9 attempted
    - signature update to match Qt 5.9 ABI/signatures
    - plenty of testing flakiness and also test crashes
  - improvements to signature tests


==== 16. November 2017 ====
* Plan for 5.14.2-1 release
- Build system cleanup. It is now possible to build only a subset of Qt modules per cmd line option
* Research on Pickling support, PYSIDE-15
  - this is not complete and may need further patches
* Provided fix for PYSIDE-1267 related to efforts of exposing QScintilla
- Added QAxContainer, more classes from 5.10
* Object dumper to help debugging python implementations
- Preparing to add Qt3D
* Debugging options for the code model.
- Removed flaky test
* pysideuic old functionality into the QUiTools module
  - further research on how pip wheels might be used for Pyside
** compileUI
  - seems to work well on win & macOS
** loadUiType
  - problems on Linux related to libICU (or in general due to different system libraries)
* Q_ENUM discussion
- implemented and tested --standalone feature for the main Qt platforms [https://bugreports.qt.io/browse/PYSIDE-558 PYSIDE-558]
- open question remains how 3rdparty Pyside deployment path might look like
- [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510]


==== 9. November 2017 ====
==== 9. April 2020 ====
- Work on simplifying the build system, made it possible to specify a module subset to build
- [https://bugreports.qt.io/browse/PYSIDE-558 PYSIDE-558] Fixing rpaths and making --standalone work on the 3 platforms. Result: Self-contained binary wheels. Needs Review.
- Trying to setup the project for building the docs. I managed to build the rsts from the patch in gerrit but running sphinx on those rsts results in errors about python 2 style code.
- [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510] work continued


==== 2. November 2017 ====
* Most bugs reported in 5.14.2 are fix on 5.14
- Releasing:
** Preparing the process for the release of 5.14.2-1
  - continued work on macOS installer
** Check about versioning on pypi to not override 5.14.2 wheels.
  - binaries must be patched during the install from repo (rpath setting)
* PYSIDE-813 is now fixed
  - adopting the scripts from Qt for Pyside
* PYSIDE-1255, Signals not being emitted.
  - made pip install work on Mac -> would be alternative to online installer approach
* Working on Q_ENUM
      - two deployment choices available
- discussions on how void* pointer should be handled, two options on the table
  - add additional Pyside module handling such pointers
  - add feature to shiboken to transparently add the support to any arbitrary C++/pyside project using shiboken
- documentation snapshot generated
- simplified setup-pyside and related build script options


==== 26. October 2017 ====
==== 2. April 2020 ====
- Releasing:
  - test repo for online installer created (mac seems to deploy)
  - first evaluation of suggested installer approach on various platforms
- Documentation:
  - Qt doc team joined the effort
  - first experiences are collected
  - should new documentation be done in rst rather than qdoc format?
  - Getting started, General platform requirements and general fixes turning up during generation
- [https://bugreports.qt.io/browse/PYSIDE-571 PYSIDE-571] received further fixes and reviews
- REDHAT not working on Coin (caused by gcc header issues)
- other minor improvements


==== 19. October 2017 ====
* 5.14.2 is out:
- Discuss open Pyside 2 release & documentation
** keep an eye on new bug reports.
- Release packaging suggestion
*** https://bugreports.qt.io/browse/PYSIDE-1253
  - Qt for Python installed via Qt installer and python scripts pointed to module via PYTHON_PATH
*** https://bugreports.qt.io/browse/PYSIDE-1254
  - create test online repository for Qt installer
*** https://bugreports.qt.io/browse/PYSIDE-1255
  - follow up how this Pyside installation approach might impact deployment of Python apps using Qt for Python
** The new documentation is out too: https://doc.qt.io/qtforpython/
  - Linux distros shipping Pyside? (not sure yet either)
* 'manylinux1' discussion
- coin
* CI status
  - breakage in CI provisioning due to competing Python binaries coming from MSVC 2017
* 'loadUiType' status https://bugreports.qt.io/browse/PYSIDE-1223
  - coin template needs updating
** two approaches for it, a Python and another in C.
- [https://bugreports.qt.io/browse/PYSIDE-571 PYSIDE-571] work progressing (ready for review)
* PYSIDE-813
- lots of fixes in Pyside dev branch and
** Finding where the reference is gone, but there is the only issue left.
- feedback from Qt World Summit:
** All the other issues were solved.
  - is Pyside on Android and iOS?
** A solution should be out soon.
  - iOS probably out since platform cannot have interpreted code
* Research on adding Python support for Qt's lupdate: PYSIDE-1252
  - Scriptable application use case was a sought after feature
  - qdoc got WebXML patch -> open question which version to use for doc generation across the various pyside versions
    - add script to support single command to generate documentation


==== 12. October 2017 ====
==== 26. March 2020 ====
- no update due to Qt World Summit 2017


==== 05. October 2017 ====
* 5.14.2 Release
- Qt DataVisualization port has finished including an example
* OKRs Update
- Coin no progress due to pending Qt 5.9.2 release
** Looking for commercial opportunities
- webxml support being implemented inside qdoc (beginning of the pyside documentation toolchain)
* PYSIDE-813 new discoveries found:
** There are a couple of issues with one of the PYSIDE-803 patches that will be solved soon.
** PYSIDE-164 is out of the picture
* Lambda functions for QWebEngineCallback PYSIDE-946 so we can expose the missing bindings.
* QVariant conversions tweaks PYSIDE-1250
* Working on adding 'loadUiType' into PySide PYSIDE-1223
* Research on adding Python support for Qt's lupdate: PYSIDE-1252


==== 28. September 2017 ====
==== 19. March 2020 ====
- 5.6 and 5.9 branches are *finally* enforced by CI - yeeeaaahh
- Dev branch is still missing some forward merges before it can be enabled.
- port of QtDataVisualization progressing
- fixed bugs: [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510], [https://bugreports.qt.io/browse/PYSIDE-517 PYSIDE-517], [https://bugreports.qt.io/browse/PYSIDE-562 PYSIDE-562], [https://bugreports.qt.io/browse/PYSIDE-564 PYSIDE-564]
- [https://bugreports.qt.io/browse/PYSIDE-156 PYSIDE-156] in progress, first example of qApp protection, benchmark of impact ongoing


==== 21. September 2017 ====
* 5.14.2 Release preparations
* Work on Widget gallery example
* Done: Refinements to wheel-tester.py
* Done: Reworked test_wheel.py for macOS
* Done: Fixed PYSIDE-1247 signature warning in Python 3.6
* In progress: Instrumentation of PYSIDE-164/813


- Prototyping and exploring of Pyside packaging options
==== 12. March 2020 ====
- [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510] done and merged
- [https://bugreports.qt.io/browse/PYSIDE-156 PYSIDE-156] being addressed thanks to [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510]
- [https://bugreports.qt.io/browse/PYSIDE-487 PYSIDE-487] Qt Data Visualization port progressing


==== 14. September 2017 ====
* CI Status
- Coin
** Everything up and running
  - 5.6 testing is back online (5.9 target unblocking pending a merge)
** 5.14.2 to be released next week hopefully.
  - Packaging of Pyside started to become a discussion topic
* PYSIDE-803
      - Standard PIP deployment
** Almost there!
      - Separate delivery via the usual Qt account channel
** retrieveMetaObject improvements.
- void* support has a pending patch (https://codereview.qt-project.org/#/c/205124/ and related example https://codereview.qt-project.org/#/c/205272/)
** We will try to test it without the allow-thread patch to evaluate performance.
- Documentation work ongoing
* PYSIDE-813
  - WebXML support was added to qdoc - see [https://bugreports.qt.io/browse/PYSIDE-363 PYSIDE-363]
** we will keep PYSIDE-164 open until we find a solution that fixes both.
  - inputting the resulting WebXML to shiboken gave promising results
* Starting to evaluate std::function compatibility with Shiboken.
  - Qt Creator gain ability to fold away Python license headers
- Signature patch (https://codereview.qt-project.org/#/c/198654/)


==== 7. September 2017 ====
==== 5. March 2020 ====
- Pyside CI broken (timeout for tests is zero)
  - Pyside provisioning scripts are very fragile
  - Qt's own  provisioning is interfering when e.g. Pyside relevant tools get changed by Qt
  - new ideas and redesign is likely to be needed
- New Bindings: QRegularExpression, QVersionNumber, QUuid,
- Discussions around Documentation for pyside
  - couple of options for generation pipeline
    1.) qdoc generates WebXML -> Shiboken converts WebXML to ReST (used to work in Qt 4 days)
    2.) qdoc is lib which creates AST - > shiboken uses the AST to generate ReST
    3.) \pyside to document python classes (lots of documentation effort and not ReST integratable)
    4.) minimalistic approach is to merely link to the Qt object class reference (python specific docs are somewhat separate
- [https://bugreports.qt.io/browse/PYSIDE-516 PYSIDE-516] further investigation how to deal with void* APIs
  -> prototyping ongoing
- [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510] redesigned once again (no more internal Python dependencies, Python version independent implementation)
 
==== 31. August 2017 ====
- 5.9 passes on all platforms but one (10.10 still failing)
  -> fix for provisioning scripts pending
- 5.6 no problems at hand (all passing)
- [https://bugreports.qt.io/browse/PYSIDE-516 PYSIDE-516] hit a dead end
  -> fundamental way of passing vertex data (void*) pointer between Python and C++ not addressed yet
- [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510] complete


==== 24. August 2017 ====
* CI Update
- Coin 5.9 provisioning is in place, but there are some issues with paths to tools which are being addressed
** Including Python 3.8
- Build issue on Windows 10 5.9 branch, addressed by patch in review https://codereview.qt-project.org/#/c/203406/
** Maybe using alternatives to have many Python versions.
- Fix to macOS build when old Qt 4.8 is present, addressed by patch https://codereview.qt-project.org/#/c/203313/
* Priority bugs
- [https://bugreports.qt.io/browse/PYSIDE-516 PYSIDE-516] progress on bringing in more of the QOpenGL classes
** PYSIDE-803
- [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560] stable ABI was investigated, decision is required
*** major changes in (caching)
- [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510] finalizing license modifications
*** still other minor patches to be merged.
- [https://bugreports.qt.io/browse/PYSIDE-156 PYSIDE-156] ongoing implementation for fixing qApp crashes
*** allow-thread patch has a bug, maybe this can be detach from the snippets one.
- [https://bugreports.qt.io/browse/PYSIDE-552 PYSIDE-552] in process of being merged
** PYSIDE-813
- [https://bugreports.qt.io/browse/PYSIDE-562 PYSIDE-562] pending patch
*** PYSIDE-164 appears again if we fix it,
- [https://bugreports.qt.io/browse/PYSIDE-563 PYSIDE-563] in process of being merged
*** Maybe a solution is to fix 164 in another way.
- PySide 2 presentation being prepared for Qt World Summit 2017
* 5.15 feature status
* Changes for Qt 6
** Changes in the [https://codereview.qt-project.org/c/qt/qtbase/+/284225 QMetaType representation]
*** Reference of the [https://codereview.qt-project.org/c/qt/qtdeclarative/+/285788 new system in qtdeclarative]
** Wishlist for [https://bugreports.qt.io/browse/PYSIDE-904 Qt6 opportunities]


==== 17. August 2017 ====
==== 27. February 2020 ====
- Almost everyone is still on holiday - not much progress
- PySide 5.9 branch CI changes are still pending integration / ongoing due to issues with the CI infrastructure switch
- Investigation ongoing regarding QSSL classes on 5.9 branch
- PYSIDE-510 - ongoing work to make separation of different licensed code
- PYSIDE-156 - initial work to stop crashes when using methods that require an allocated QApplication instance
- PYSIDE-558 - initial investigation on how to proceed
- Updated the PySide2 wiki documentation to clear up build steps and requirements.


==== 10. August 2017 ====
* CI Updates
- holiday time is hampering project at the moment -  not much progress
** 5.12 cherry-picks
- CI changesin Qt affected Pyside project such that focus was on different CI matters
* qApp
- [https://bugreports.qt.io/browse/PYSIDE-557 PYSIDE-557] being addressed
** Deprecation message or alias (when using QtWidgets.qApp)
- some very minor issues were fixed
* PYSIDE-803
** Missing patches to be merged
*** Python 2.7 issues
*** allow-thread commit message (add a changelog)
*** second caching mechanism to be studied after we merge the first set of patches.
*** Third attempt after the stackless gilstate approach
** Documentation
* Python 3.8 testing is still being worked out


==== 03. August 2017 ====
==== 20. February 2020 ====
- PYSIDE-510 under code review https://codereview.qt-project.org/198654
  - > license issues have to be addressed
  - > some testing aspects still open (delayed till later on)
  - > investigation of impact on deployment across multiple python run-time versions required
- missing bindings script/wiki page updated: [[PySide2_Missing_Bindings|Missing PySide2 bindings]]
- first working array support has been delivered (some adjustments still required), now proceeding to extend for OpenGL [https://bugreports.qt.io/browse/PYSIDE-516 PYSIDE-516]
- Missing classes in works (e.g. QAbstractnativeEventFilter, QFileLock,....)
  - > revealed some issues of handling void* pointers


==== 27. July 2017 ====
* CI Updates
- Fix for [https://bugreports.qt.io/browse/PYSIDE-331 PYSIDE-331] causes lots crashes in auto tests
** Cherry-picking some changes to 5.12 to fix the virtualenv 20 issues.
  -> more investigation ongoing
** macOS timeouts
- coin
** possibility of merging simple changes directly.
  - since 5.6 is now enforced by Qt CI the focus shifted to the 5.9 branch of Pyside
* qApp issues
  - still encountering build issues on 5.6 though
** Patches ready for review
  - cmake upgrade for macOS 10.10
* PYSIDE-803
  - missing virtual env for macOS 10.12 being deployed
** Patches needs some polishing
  - msvc 2013 being removed from CI targets
* Testrunner improvements
  - clang on OpenSuSE deployment ongoing
** stdout/stderr issues with ctest on windows
  - lots of effort went into debugging the above Coin issues
** smart pointers tests crashing, due to qApp issues.
- numpy support for 2d array feature development progressing ([https://bugreports.qt.io/browse/PYSIDE-354 PYSIDE-354])
** Python 3.8 is also giving problems (DLLs missing)
** debug builds on windows does not work.
* Shiboken documentation being reorganized
* Starting testing Python 3.9


==== 20. July 2017 ====
==== 13. February 2020 ====
- coin
  - license test passing
  - setup issues wit Python 3 and msvc 2008 vs 2015 issues
  => need to install newer Python 3 binaries
  => otherwise looks like enforced testing can be set alive on 5.6 branch
  - 5.9 still having clang header issues
- 2D array support work in progress
- [https://bugreports.qt.io/browse/PYSIDE-331 PYSIDE-331] -> waiting for PYSIDE-510 dependency
- [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510]-> issues with Python 2.x left
- need to get a handling what functions are not supported by pyside due to exclusions or missing support in shiboken


==== 13. July 2017 ====
* CI updates
- coin
** Windows package signing will be possible, hopefully soon.
  - Production coin was updated today and all fixes are finally executed
* Documentation updates
  - 5.6
** Example gallery
  - macOS 10.11 machines have Python 2.6, which causes test script to fail due its usage of a
** WebChannel example merged,
          module added in 2.7. Investigation in progress on the best way to fix this.
* Python 3.8 changes on Windows are still being tackled.
  - build failure with Windows 8.1 (msvc2013-x86)
* Bugs
  - 5.9
** PYSIDE-803 status: A patch waiting for review is there, but we need to combine it with the other solutions we currently have. Still, there are some corner cases where the problem is not properly solved.
  - macOS 10.12 missing virtual env (https://codereview.qt-project.org/200006)
** qApp issues to be solved, but we will remove the import features. qApp will remain as a built-in.
  - Rest Linux/macOS configs are failing various build issues
* OKRS 1Q/2020
  - dev is still pending for qt5 merge from 5.
- [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510] development completed, test added, needs review
- [https://bugreports.qt.io/browse/PYSIDE-331 PYSIDE-331] ongoing work
- [https://bugreports.qt.io/browse/PYSIDE-550 PYSIDE-550] investigated, needs a working solution to allow proper building on distros that separate Qt private headers into separate packages
- [https://bugreports.qt.io/browse/PYSIDE-354 PYSIDE-354] ongoing work on C / C++ array support in PySide, some questions remains on how to deal with xml syntax and multiple dimensions.


==== 29. June 2017 ====
==== 6. February 2020 ====
- coin
  - Qt 5.6 all coin changes for Pyside are done but waiting for coin production update (after Qt 5.9.1 release)
  - Pyside/Qt 5.6 on new OpenNebula infrastructure confirmed to run
  - Qt 5.9 based setup still misses clang libs (merge pending)
  - Pyside/Qt 5.9 test failure fixes on macOS
- worked on array support (passing arrays between Pyside and Qt API) - work in progress ([https://bugreports.qt.io/browse/PYSIDE-354 PYSIDE-354])
- continued work on debug builds across the platforms
- embedded Python example under review (further testing across the platforms)
- [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510] finished (not yet merged) -> revealed a few more  problems in [https://bugreports.qt.io/browse/PYSIDE-331 PYSIDE-331] & [https://bugreports.qt.io/browse/PYSIDE-308 PYSIDE-308]
- added a way to dynamically detect the available Qt modules in Pyside


==== 22. June 2017 ====
* CI status and issues with the Qt provisioning 5.12
- building pyside on Win with debug and non-debug
** 5.12.7 release will take more time to add new features.
- QSSL* classes do not build on macOS & Windows (patch in progress)
** 5.14 has some issues with OpenGLFunctions.
- dll name handling work finished (build system issues were addressed)
* Documentation: Interest for the new shiboken2 documentation structure and usage of the ApiExtractor.
- PYSIDE-531 discussions
* Python 3.8 compatibility with older branches.
- coin
* Updates on PYSIDE-803 [https://bugreports.qt.io/browse/PYSIDE-803?focusedCommentId=496894&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-496894 link]
  - followup from 18 May (windows issues in coin)
* Suggestion about iterations a-la-python https://bugreports.qt.io/browse/PYSIDE-1216
  - test runner changes being merged should address this
* Events
  - new regression on macOS targets though
** Qt World Summit 2020 Palm Springs
  - 5.9 issues due to clang continue to exist (will be addressed after 5.6 is enforced)
** PyCon US


==== 15. June 2017 ====
==== 30. January 2020 ====
- dll name handling fixed across the platforms (e.g. pkgconfig handling)
* 5.14.1 release rolling
- PYSIDE-500 fixed
* Work on [https://bugreports.qt.io/browse/PYSIDE-1204 PYSIDE-1204]
- PYSIDE-331 is still not done (in parts a module by module fix is required)
* Work on [https://bugreports.qt.io/browse/PYSIDE-1191 PYSIDE-1191] PySide2 5.14 source now builds against Qt 5.12 as well
- PYSIDE-510 ongoing
* Further research on [https://bugreports.qt.io/browse/PYSIDE-803 PYSIDE-803]
- no further progress on coin
** full instrumentation of generated source for tracing,
- Getting started guide has been updated dealing with Qt 5.6 and Qt 5.9 based Pyside builds
** discovery of new hooks to support. Still in flux.
- scriptable Pyside example been developed to demonstrate SDK-like usage of Pyside
* Fixed some issues of Python 3.8 (most prominently warnings about implicit conversion to integers for QFlags), will be fixed in 5.14.2
- lots of small infrastructure changes/fixes
* qApp macro [https://bugreports.qt.io/browse/PYSIDE-1178 PYSIDE-1178] [https://bugreports.qt.io/browse/PYSIDE-1158 PYSIDE-1158] [https://bugreports.qt.io/browse/PYSIDE-1135 PYSIDE-1135] finally closed. One cleanup check in may follow.


==== 8. June 2017 ====
==== 23. January 2020 ====
- Proposed solution for PYSIDE-500
* Fix for CI/macOS problem is in, but it requires some merges in Qt5. Until all required merges are done, we will use Qt5 5.14.1 with Qt For Python 5.14
  - Further work on example for PYSIDE-526, work on shiboken2 command line handling to ease usage with qmake
* Research on [https://bugreports.qt.io/browse/PYSIDE-803 PYSIDE-803]
- Updated Getting started Wiki
* Proposed an "until" attribute for typesystem files to make it possible to build Pyside 5.14 against Qt 5.12 [https://bugreports.qt.io/browse/PYSIDE-1195 PYSIDE-1195]
- Introspection work continued (PYSIDE-510)
* Improved the view of compare app for [https://bugreports.qt.io/browse/PYSIDE-803 PYSIDE-803]
* Analysis of PyQt5 and SIP implementation


==== 1. June 2017 ====
==== 16. January 2020 ====
- PYSIDE-500
* CI/macOS problems are being worked.
- https://wiki.qt.io/PySide2_GettingStarted needs a serious cleanup
* qApp fix waiting to be merged.
  - 5.6 vs 5.9 differences not explained
* first attempts to tackle [https://bugreports.qt.io/browse/PYSIDE-803 PYSIDE-803]
  - specify exact version matching conditions
* Python 3.8 fix to old branches is required for distributions using 5.12 LTS like Conda.
- pyside repo merge completed
* Working on Q_ENUM support.
  - Coin changes required to catchup - > recent CI issues have caused delay
* Viewer for [https://bugreports.qt.io/browse/PYSIDE-803 PYSIDE-803] is ready to try. Please check out https://git.qt.io/playground/pyside-compare.git and give feedback.
- Introspection work continued (PYSIDE-510) -> not yet complete
- qtcharts and related examples have been ported (5.9 only)
- license header checks of Pyside for Coin able to distinguish branches
- Array support for Pyside missing (numpy_array support?)


==== 18. May 2017 ====
==== 9. January 2020 ====
- Coin
* [https://bugreports.qt.io/browse/PYSIDE-1185 PYSIDE-803] needs to be tackled soon, it's critical, and we cannot carry that into Qt6.
  - Win nodes didn't run the cleanup functions -> test failures due to artifacts -> no solution yet
* Python 3.8.1 on Windows has [https://codereview.qt-project.org/c/pyside/pyside-setup/+/285797/ some issues] while building.
  - Clang issues persist and this must be addressed in the broader scope of Qt/qdoc depending on libclang too
* qApp macro changes [https://codereview.qt-project.org/c/pyside/pyside-setup/+/285655 discussion].
    -> until this point in time the setup is a manual one for pyside/5.9+
* documentation updates are still pending.
- merge of psyide repositories -> no objections against the plan in the community
* with the release of 5.14 we have been fixing many details from uic's Python support.
  -> merge will happen in the next few days (pyside.git, pyside-setup.git and shiboken.git become one repo)
* designer's RUNPATH [https://codereview.qt-project.org/c/pyside/pyside-setup/+/285712 needed to be patched], waiting for approval,
  -> examples, wiki and tools will remain as they are
* A modular way of packing wheels is being studied.
- QOpenGL* porting continuing
* Re-take the Python extensions for QtCreator project evaluation.
- qttext2speech ported to Pyside2
- failing QML tests in Qt 5.9 based Pyside
- PYSIDE-510 - introspection solution in the works
- Qt World Summit Berlin 2017 (talk for Pyside being handed in)


==== 12. May 2017 ====
== 2019 ==
- looked into the Windows tests failures, and the reason might be related to how we copy around build artifacts, leading to an incorrect folder structure. Coin team to look at it.
* [[Qt for Python Development Notes 2019]]
- Fixed a small regression in 5.9 with building on macOS after some cmake changes that happened in 5.6
- Implemented, tested, reviewed and committed the multimedia widgets examples
- documentation from Pyside1 days can not be generated anymore
  -> new approach required using exiting Qt5 doc tools
- QOpenGL* port to Pyside has started -> missing support for arrays in shiboken
  - more thorough design discussion needed
- Coin
  - provisioning for clang in Qt CI ongoing: https://codereview.qt-project.org/#/c/192517/10


==== 04. May 2017 ====
== 2018 ==
- Coin
  - libclang 4.0 provisioning available (code reviews ongoing -> enabler for Pyside and qdoc testing)
  - 5.6 coin issues resolved
  - macOS related CI/cmake failures were resolved
  - some CI sync issues among pyside submodules (always submodules HEAD is tested)
  => may have to change once we come closer to the final release ->
  => fine as long as we are in heavy development mode
  - discussion around Ubuntu and OpenSuse configurations
  - minimal cmake requirements not met on all distros
    - 5.6 only be build using RedHat 6.6
    - 5.9 builds have updated Linux distros -> may be able to obtain a new cmake version without hacking the standard toolchain
- QtMultimedia and QRaster* API bindings further completed
- added tests and examples for the above bindings/APIs
- PYSIDE-510 (required for simplified and more generic testing of bindings)
- PYSIDE-504 work is ongoing
- PYSIDE-507 -> avoid hardcoded includes when certain Qt modules are not available
- brief discussion whether to merge the shiboken and pyside repo
  -> advantages from a CI perspective and reduces pyside setup complexity


==== 26. April 2017 ====
* [[Qt for Python Development Notes 2018]]
- Coin
  - provision for 5.9+ branches -> we would like to use libclang 4.0
  - test still not yet executed due to branch mismatch which pulls in dev branches
- missing bindings in QtCore/QtGui/QtMultimedia - work in progress
- clang support done (except for a Mac issue)
  - Pyside clang version required Qt 5.7 or later
- [https://bugreports.qt.io/browse/PYSIDE-500 PYSIDE-500] done
- work on PYSIDE-500, 502, 504, 497 will continue
- qdoc work started trying to recover whatever documentation is left from Pyside 1.x
 
==== 20. April 2017 ====
- Fix for [https://bugreports.qt.io/browse/PYSIDE-331 PYSIDE-331] broke the Windows build; under investigation
- Refactoring, fixed build warnings
- Looked at debug builds on Windows
 
==== 13. April 2017 ====
- discussion around merge policies between 5.9 and 5.6 branch
- Linux debug library issues fixed
- PYSIDE-488 fixed via workaround
- fixed a unit tests
- worked on qdoc/html generation in Pyside (failed so far - waiting for qdoc maintainer feedback)
- PYSIDE-331 patches merged -> more bugs found in the meantime
 
==== 6. April 2017 ====
- 5.6 branch created
- 5.9 branch to be created as well (easier setup for Qt 5.9 testing in Coin)
- Coin
    - not passing build platforms have been disabled
    - otherwise COIN passing on 5.6 (except for 2 failing test) -> soon to be enforced
    - license checker passing in dev
- clang changes merged to dev branch (after reviews)
  - clang provisioning on Coin still missing
- for now shiboken is not a generic C++ bindings generator (targeting Qt use cases only)
- TODO: enabling the generation of documentation from repos
- fixed mixed usage of debug and release build (no debug builds for windows)
- [PYSIDE-331] work continuing - fixed, tests are missing
 
==== 30. March 2017 ====
- Coin
    - some platforms passing and will be enabled by default
    - MinGW, some OSX and cross compile targets remain out
- will branch pyside dev branches to 5.6, new dev becomes clang branch
    - regular merges from 5.6 -> dev will start happening
    - Pyside 5.6 branch will continue to work against Qt 5.6
- need reviews for [https://bugreports.qt.io/browse/PYSIDE-323 PYSIDE-323] to merge clang changes
    - Qt 5.10, 5.9 (on main desktop plawtforms working)
    - for now the Pyside dev development will be based on Qt 5.9 (to be bumped up later on)
- [PYSIDE-331] - in progress
- [PYSIDE-156] -
 
==== 23. March 2017 ====
- Coin
  - progressing
- More tests fixed
- wip/clang branch created, will receive Clang parser port with instructions
- Refactoring of shiboken, replaced QtXml classes by QXmlStreamReader allowing for stricter error checking
 
==== 16. March 2017 ====
- Coin
  - the fixes are still integrating or are under review (no further progress until this is done)
- clang parser replacement [https://bugreports.qt.io/browse/PYSIDE-323 PYSIDE-323]
  - most test failures related to clang are fixed
  - tests ran pretty much through on Qt 5.9 (Windows and Linux - Mac not yet verified)
  - code cleanups in shiboken
  - will create feature branch on all pyside repos to get the clang patch series under CI control
  - merges from regular pyside branches into clang branch will commence
  - readme required that explains how clang is to be built (if not provided by platform)
- [PYSIDE-331] - in progress
 
==== 09. March 2017 ====
- Coin
  - lots of changes in Gerrit for Pyside and coin
  - the outcome has to be check once everything merged
  - upcoming clang dependencies in shiboken introduces new requirements for Coin
  - clang changes to be dealt with after pyside branching
- clang
  - first complete bindings generation with Qt 5.6 and Qt 5.9
  - some failing unit tests which have to be looked at individually
  - actual merge depends on pyside branching which in turn depends on recent Coin changes
- smart pointer support
  - patches generally done, gerrit review ongoing
  - rather large patch
- created list of missing bindings in Pyside ([https://wiki.qt.io/PySide2_Missing_Bindings Missing Bindings])
  - mostly class level view, global functions at al not covered
- Jira cleanup
  - PYSIDE-464, PYSIDE-217, Pyside-224 fixed
  - most bugs reviewed now and valid ~100 bugs were identified
 
==== 02. March 2017 ====
- Coin
  - Coin runs tests on Windows and OSX (some failures in the test - to be investigated)
  - Windows provisioning somewhat blocked due to CI issues
  - no progress on Linux
  - OSX 10.8 ran tests with expected results
  - OSX 10.9 has issues due to Pyside not supporting namespace builds of Qt
- clang
  - preprocessor has remaining issue
      -> with clang compiler but gcc seems OK
      -> Qt Core wrapper close to compiling (QHash issues remaining)
- Smart pointer work continues
  - some uses cases work, other use cases might remain
- [https://bugreports.qt.io/browse/PYSIDE-364 PYSIDE-364] was fixed (patch pending)
- General error review on bugreports.qt.io
  - 50% done (prioritized bugs are handled/checked bugs - "done" bugs)
- ran address and leak sanitizer over Pyside which resulted in some worrying cases (need to be addressed going forward)
 
==== 22. February 2017 ====
- [https://bugreports.qt.io/browse/PYSIDE-462 PYSIDE-462] Improved solution approved
- [https://bugreports.qt.io/browse/PYSIDE-205 PYSIDE-205] Hard-to-detect memory leak plugged
  - slow memory leak found in shiboken with thousands of false positives
  - used differential analysis of valgrind output
- Clang: Fixed Preprocessor handling (set defines, include paths), got minimal binding tests to pass, now adapting MetaBuilder and PySide to what Clang finds when parsing Qt. Good news: Very little need to set Q_DOC or other magic defines
- Coin: Slow progress, currently struggling with provisioning
- extensive bug triaging ongoing in Pyside Jira project
 
==== 16. February 2017 ====
- Coin (no update - other priorities in release/CI team)
- Clang (progressing on pre-processor work)
- PYSIDE-315 closed
- PYSIDE-462 more review needed
- Shared pointer API very slowly progressing (lots of different fixes needed)
- QMimeDataBase support added
- QUrlQuery support blocked on QDOC defines in Qt sources (shiboken sets the wrong define)
- chasing memory leaks (PSYIDE-205)
- extensive bug triaging ongoing in Pyside Jira project
  - confirming and testing the reported bugs (70 of 200 processed)
  - some smaller bugs were fixed in the process
- quite a few bugs were discovered this week while working on the above items, e.g.:
  - deployment of pyside applications partly broken due to hard-coded install paths in Qt libs
  - Qt events are swallowed when Pyside error/exception occurs
-
 
==== 9. February 2017 ====
- Clang progressed
  - pure C++ tests for API extractions are passing (C++ parsing based on clang)
  - even works with cmake
  - old C++ preprocessor still to be replaced
  - working through old preprocessor and checking what magic it did and how clang might be able to replace it
- PYSIDE-315 & PYSIDE-462 fixes pending for review
- COIN
  - continue progress an getting more platforms to pass (unblocking one step at a time)
  - Windows (32bit) and mac are building, Win 64bit still not building
  - OSX and Windows are stopping in the test runner phase
  - missing cmake update still on Linux (provisioning update required)
 
==== 26 January 2017 ====
- PYSIDE-315
  - principle fix merged but some minor improvements still pending
- Pyside-462
  - essentially a feature request as C++ default parameters are not yet supported by Pyside
  - discussion ongoing how to address the problem
- COIN
  - 10.11, 10.9 & 10.8 build passes
  - 10.10 still failing during build
  - Progress on Windows and running into new problems further down the path
  - Redhat failed to general brokenness of the platform in CI
  - Ubuntu no further progress
- clang parser work progressing
  - completeness of work is currently measured by passing unit tests
  - there is a long way to go
  - see [https://bugreports.qt.io/browse/PYSIDE-323 PYSIDE-323] and associated patches for progress monitoring
- Fixed regression which prevented Pyside to compile with Qt 5.5.1
- shared pointer support
- no update on 2nd February 2017 (next week)
 
==== 19 January 2017 ====
- PYSIDE-315
  - a possible fix is pending, some minor performance improvements are still possible
  - caused by different signal/slot ordering in Qt4 and Qt 5
- COIN
  - issues on 10.8 and 10.9 platforms should pass now
  - 10.11 & 10.10 still have issues
  - Windows timeout problem fix in COIN (but no COIN update until 5.8.0 released)
  - Linux builds are failing
    - Ubuntu 14.04 fails due to cmake issue
    - Redhat 6.6 & OpenSuse 13.01 deferred
  - current COIN freeze for 5.8.0 release affecting patching of COIN for Pyside
  - next steps in priority -> run tests on 10.8/10.9 and get Linux running
- PYSIDE-79 regression fixed as well (some interaction between PYSIDE-315 & PYSIDE-79)
- PYSIDE-462 to be looked at next
- clang parser work progressing
 
==== 12 January 2017 ====
- PYSIDE-315
  - sorting of slots/signal connection changed on Qt side and Pyside side has not caught up
  - had similar connection issues on the QML side, need to investigate whether there is a connection
- PYSIDE-79
  - caused a regressions (not yet investigated)
- fixed OpenGL types not being recognized on MacOS (partly fixed)
- API's with shared/smart pointers in Qt don't work
  - has potential long term effects and investigation has started into the reasons
- Refactoring shiboken in preparation for clang
- COIN currently runs tests with namespaced Qt
  - short term fix to exclude namespaced Qt builds with Pyside (broken on MacOS 10.9)
  - other failures: missing libraries on MacOS (10.11), missing provisioning on Windows, cmake issues on 10.10
  - unknown state on Linux (current Redhat too old)
- Prioritization after status round:
  - PYSIDE-315 to be investigated based on recent signal/slot patches for QML
  - Smart pointer issues reduced in priority to provide space for PYSIDE-315 & PYSIDE-79 regression
- verify that COIN runs testrunner (not just building Pyside)
  -> not yet verified since we are still failing builds in COIN
 
==== 5 January 2017 ====
- COIN update
  - COIN changes merged (no further patches pending)
  - need to run an integration test
  - issues related to different build platforms still to be expected
- Continue with clang
  - backtracking a bit (reusing some node API's during parsing but otherwise use clang to populate the tree)
- test blacklisting reviewed (some removed - mostly signal related ones, one new regression)
- regressions in QtQuick were worked around (caused by recent Qt Quick changes)
- issues with macos framework style includes in Qt
- PYSIDE-315 debugging ongoing, very hard to track down
    - was it a regression from a previous Pyside release (e.g. Qt 5.4?!?
- hard-copied Qt 5.4 based headers still in existence
  - updated needed but would shut Qt 5.4 users out
</div>
 
== 2016 ==
<div class="mw-collapsible mw-collapsed" style="overflow:auto;">
 
==== 22 December 2016 ====
- lots of discussions around the COIN patches
  - source archive setup being under review
  - Qt 5.6 provisioning patches merged
  - CI uses Python 2.7 at this stage
- clang C++ parsing continues
- fix of some Pyside unit tests (now have a clean slate again)
- finished QtQuick port
- some overflow problems have been fixed in shiboken
 
==== 15 December 2016 ====
- COIN changes pending for testing infrastructure
    -> https://codereview.qt-project.org/177136 (Pyside change)
    -> https://codereview.qt-project.org/176968 (Coin change)
    -> https://codereview.qt-project.org/179662 (Provisioning changes)
    -> https://codereview.qt-project.org/179663 (Provisioning changes)
- waiting for COIN development team to review/accept the pending changes
- no update in PYSIDE-315 (under investigation)
- Flushed out a couple of shiboken, QML, qml example bugs
- Some bugs related to parser delayed until clang parser task done (https://bugreports.qt.io/browse/PYSIDE-322)
- most basic shiboken API extractor test to pass (global enumeration test)
- some trouble with int size data types
    -> Python 2 & 3 are different and the relevant C++ data types are yet again different from platform to platform
 
==== 8 December 2016 ====
- COIN patches pending approval
  - Windows provisioning reviewed
  - Linux, Pyside, COIN itself
- Clang changes progressing, comparing AST tree from old parser and clang
- PYSIDE-79 done
- PYSIDE-315 under investigation
- QtQuick patches taking shape (some template magic and function pointer
  features in Qt cannot be parsed by shiboken)
 
==== 1 December 2016 ====
- COIN
- PYSIDE-79 there seems to be a final work around (https://codereview.qt-project.org/#/c/176374/)
    - fixing a few tests in the process
- clang update
  - dumping AST, identifying the required info
  - work in progress...
- problems with global static QObjects on the Qt side calling back into Python during app exit
  - may require some changes on the Qt side
 
==== 24 November 2016 ====
- automatic COIN triggering for submodules work in progress
  - several discussions on this topic this week
- Clang investigation (what library to use)
- fixing bugs on Qt side for Pyside
- Qt QML support almost done, work will continue with Qt Quick
- PYSIDE-79 work story continues
  - reference counting not quite accurate but point of deallocation of ref count not identifiable
 
==== 17 November 2016 ====
- Pyside team suffering from sickness -> not much progress this week
- Pyside-79 fix had a lot of negative side effects (breaking existing tests)
  - internal object reference counting is the predominant issue at hand
  - continue to work on the bug (no resolution yet as delayed due to sickness)
- COIN some progress but still open discussions on branching policy required
 
==== 11 November 2016 ====
- PYSIDE-79 being fixed
- PYSIDE-315 to be addressed
- Shiboken and Clang
  - familiarizing with clang and its parser's inner working
  - added experimental qmake project definition for shiboken (makes work in Qt Creator easier)
- Qt QML on Pyside work progressing
- work on COIN did not progress due to conflicting priorities inside COIN development
 
==== 3 November 2016 ====
- working through the QML stack esnuring all required API's are exported (https://codereview.qt-project.org/#/c/175682/)
- small build system patches
- PYSIDE-79 work progressing
- OpenGL support fixed (PYSIDE-314)
- COIN issues
    - repo interdepencies not working yet, suggestion under discussion and to be implemented
    - most license checks have been fixed
    - Qt 5.6 based Pyside to skip check
    - after branching for C++11 work the dev branch should work from license check perspective
    - eventually the entire CI needs to run through (more hidden problems could be hidden)
- Started working on C++11 compliant parser for shiboken
    - libclang will be used
    - first target is to replace the AST tree implementation
    - requires clang setup in the CI
 
==== 27 October 2016 ====
- Work on WebKit/WebEngine support
- Further work on [https://bugreports.qt.io/browse/PYSIDE-431 COIN] support
- Planning meeting
- Workshop for C++11 support in Pyside ([https://bugreports.qt.io/browse/PYSIDE-323 PYSIDE-323])
 
==== 20 October 2016 ====
- [https://bugreports.qt.io/browse/PYSIDE-355 Qt Quick support] submitted
- [https://bugreports.qt.io/browse/PYSIDE-314 QtOpenGL support] submitted
- Further work on [https://bugreports.qt.io/browse/PYSIDE-431 COIN] support, license headers
==== 13 October 2016 ====
- Qt CI update
  - Coin changes have merged but integration not yet working
  - Qt CI enables on Pyside side merged
  => COIN integration fails with license issues
  => requires review of license conditions for all files, some files are not even relicensable
  => skipping license check for now, most likely to be done later again but requires changes to license check script
  - more issues of interworking between QtCI and Pyside expected (won't be visible until license problems resolved)
  Open issue: does a change in Pyside repo trigger a rebuild of everything?
- Qt QML support progressing and first patches merged
  - serious bugs have been fixed, more complex QML examples are now working
 
==== 29 September 2016 ====
- Coin integration close but not merged
- Bugfixing in particular on the shiboken parser side
- QML/Python binding and tests fixed -> general check all day-to-day aspects of QML are working
- QML examples porting
    -> still some failing tests
    -> Check all QML/Quick class are exported
 
==== 22 September 2016 ====
- Refactored Shiboken, udnerstanding build sequences
- black list for unit tests defined and tested
- fixing of tests
- QML example fixing continued (QML bindings not working)
- Pyside side for COIN done (pending integration checks)
- COIN integration still wip due to long test and retest cycles
- pyside and shiboken repo to be relicensed similar to other Qt products
=> this should address any issues regarding the status of generated code too
==== 16 September 2016 ====
- Pyside side for CI testing ready for testing
- status of COIN side to be determined. Code exists need help from CI team to confirm status.
- build system infrastructure improvements in pyside setup
- Qt logging now working
- and more
- Update on bug handling
  - PYSIDE-88 continuing
  - PYSIDE-349 (Multimedia ported)
  - PYSIDE-344 fix pending on codereview
  - make debug builds of Pyside work (OSX works, Linux has work in progress patch, Windows side awaiting contribution)
- QML support work in progress
  - examples are slowly ported with aim to identify bugs
 
==== 25 August 2016 ====
- Properly implementing QML experience in Pyside
- Unit test fixing
- automated CI testing for Pyside
  - working locally but still failures occurring on various other test machines
 
==== 4 August 2016 ====
- Additional Pyside examples under review
- Fixed warnings coming from Shiboken
 
==== 21 July 2016 ====
 
- main Pyside 2 example port done
- additional examples to fill gaps are being ported (as per prio list)
- CI patches running, but still gaps (should be done by next week)
- about 86% of auto test working (failing count of test 80+ auto test)
- [[pyside-Teststatus|Project Test Status]]
 
==== 14 July 2016 ====
 
- Pyside 2 examples ported
- OpenGL & SVG not working
- QtQuick 2 is in strange situation (QtQml depends on QtQuick)
- Python 3 realed Unicode handling not working with Qt
- QMessageBox hangs
- no documentation for any example
- lots of warnings when building wrapper
- results: https://paste.kde.org/pgje2toyh/mlbqic
- COIN setup for pyside https://codereview.qt-project.org/#/c/158336/
- Qt 5.7 still blocked due to missing C++11 support in shiboken
    - food for ideas: https://steveire.wordpress.com/
 
 
==== 7 July 2016 ====
 
- automated CI testing
- patches for Pyside and Qt CI side required
- Testing somewhat more complicated due to closed nature of Qt CI
- script to port examples to Qt 5 -> https://bugreports.qt.io/issues/?jql=labels%20%3D%20exampleport5
- all examples to remain BSD licensed
</div>

Revision as of 11:39, 2 July 2020

2020

2. July 2020

  • Infra Update
    • Timeouts issues, increasing it is not a solution.
    • How to proceed with dev to use Qt6
      • merge without CI
      • clarify the yaml configuration
    • 5.14.2.3 new release planned
  • Selectable Features
    • snake_case for camelCase names.
    • (in progress) access Qt properties directly:
      • For 'label = QLabel("hello")', we could do 'label.text = "bye"' instead of using the 'label.setText("bye")'.
  • Qt6 compatibility
    • QML working on Linux (this will enable us to work on the registration)
  • Some improvements in the documentation generation must be done to speed up the process.
  • pyside2_config.py file to CMake
    • include XConfig.cmake files on the wheel
  • sdist package
    • nice to have: pip install -e ., but at the moment we have three egg-info directories (error)
  • Starting again with the cross compilation of PySide for embedded linux.

25. June 2020

  • Infra update
    • Release of the second set of Windows 64bit wheels.
    • Issues on the CI due to some internal issues, everything should be running soon.
  • (in progress) from __future__ import newapi
    • it's tricky to provide snake_case instead of camelCase
    • issues with tp_getattro
    • creating modified Python objects to replace the original types at runtime
  • (in progress) from __future__ import newproperties
    • Still many things to go
  • PYSIDE-1282 pthread crash solved, and will be merge in 5.14
  • Indentation fixes for generated code. Prefix adaptation for a standard format so it can be loaded in QtCreator (from warning and stuff)
  • Qt for Python 6 is partially working in some platforms
    • Still many missing modules,
    • CMakeLists.txt files needs some love,
    • Needs to adapt CI for the new dev branch
    • Windows has some issues still :)
  • libclang situation, are we sharing the same version for qdoc, qtcreator, qt, etc...?
    • Need to check in case we decide to update
  • Commercial wheels split progress

18. June 2020

  • Infra update
    • The new windows wheels still had some issues, it seems the latest are OK, and we would need to publish '_2' wheels.
    • Some issues with macOS builds for 5.15.0
  • Qt6 compatibility
  • Merged a bug fix to 5.12 (the CI was not broken)
  • (in progress) Qt6 Properties camelCase to lower_case
    • Not a trivial task
    • It's possible to rename dynamically functions, and other things.
    • Containers needs to be taken care too
    • Having more than one object with the same ID is challenging
    • Issues with str based objects
  • Fixed PYSIDE-1332, PYSIDE-1327
  • (in progress) Commercial wheel are almost ready on Linux, later some changes for Windows and macOS are required.
  • (in progress) WigglyWidget example almost there
  • (in progress) New StyleSheet tutorial.

11. June 2020

4. June 2020

  • CI Update
    • Limited API reports work
    • Improve integrations on macOS
  • Documentation updates for Qt Assistant
  • PYSIDE-1257 cx_Freeze issues seems to be related to cx_Freeze itself.
  • Q_ENUM and QFlag will be soon available.
  • New Shiboken example to expose a custom Qt Widget to Python
  • loadUiType is back into PySide (relies on pyside2-uic on PATH)
  • Other bug fixes.

28. May 2020

  • Releases
  • Documentation
  • CI Status
  • Backlog status check it here
  • QML Integration update
    • We are working on finishing the implementation of Q_ENUM, to be able to use the singletonType registration
    • Additionally, we are looking into the uncreatableType registration too.
  • Development branch for Qt6
    • We need the following before jumping into dev.
      • QList/QVector
      • QString -> integrated (clarity)

21. May 2020

  • Holiday

14. May 2020

  • CI Updates
    • CI blocked due to some provisioning issues in red hat
    • 5.14.2.2 Release is on hold
    • 5.15 commercial release in preparation
    • License check
  • 5.15 Release
    • Pickling changes
    • Examples
    • loadUiType
  • Tutorials rcc, designer
    • Add project's tutorial.
  • Continue research of using Qt6
  • __qualname__ attributes are almost done
    • This changes was required for the pickling support.

7. May 2020

  • CI Updates
    • Issues with the provisioning, for example the connection with PyPi, still in progress.
    • We will add a requirements.txt for provisioning.
  • Issues
    • PYSIDE-1255 Signal not reached in QML
    • Pickling Qt Enums PYSIDE-15
      • Almost finished, but we are waiting for PYSIDE-1285 to be fix (modulename, qualname).
    • Many other minor bugs have been fixed, but still there are a couple of strange ones.
    • First attempts to build shiboken with Qt6
    • Ideas repo re-organization
  • Features
    • Commercial addons
    • Tutorials
      • rcc
      • uic
      • QTranslator (*)
      • ...
    • QtAssistant integration
    • loadUiType
    • The new way of registering QML properties needs to be applied to the code base.

30. April 2020

  • CI Updates
    • Issues with pip upgrades
    • Planning new Python versions for new configurations.
  • Update on bugs still around after 5.14.2.1
    • 1271: Deadlock (fixed)
    • 1255: Signal not reached in QML (still in progress)
    • 1280: Research
  • Features
    • QML interaction
    • Q_ENUM and pickling SbkEnum
    • Commercial Addons

23. April 2020

16. April 2020

  • Plan for 5.14.2-1 release
  • Research on Pickling support, PYSIDE-15
  • Provided fix for PYSIDE-1267 related to efforts of exposing QScintilla
  • Object dumper to help debugging python implementations
  • Debugging options for the code model.
  • pysideuic old functionality into the QUiTools module
    • compileUI
    • loadUiType
  • Q_ENUM discussion

9. April 2020

  • Most bugs reported in 5.14.2 are fix on 5.14
    • Preparing the process for the release of 5.14.2-1
    • Check about versioning on pypi to not override 5.14.2 wheels.
  • PYSIDE-813 is now fixed
  • PYSIDE-1255, Signals not being emitted.
  • Working on Q_ENUM

2. April 2020

26. March 2020

  • 5.14.2 Release
  • OKRs Update
    • Looking for commercial opportunities
  • PYSIDE-813 new discoveries found:
    • There are a couple of issues with one of the PYSIDE-803 patches that will be solved soon.
    • PYSIDE-164 is out of the picture
  • Lambda functions for QWebEngineCallback PYSIDE-946 so we can expose the missing bindings.
  • QVariant conversions tweaks PYSIDE-1250
  • Working on adding 'loadUiType' into PySide PYSIDE-1223
  • Research on adding Python support for Qt's lupdate: PYSIDE-1252

19. March 2020

  • 5.14.2 Release preparations
  • Work on Widget gallery example
  • Done: Refinements to wheel-tester.py
  • Done: Reworked test_wheel.py for macOS
  • Done: Fixed PYSIDE-1247 signature warning in Python 3.6
  • In progress: Instrumentation of PYSIDE-164/813

12. March 2020

  • CI Status
    • Everything up and running
    • 5.14.2 to be released next week hopefully.
  • PYSIDE-803
    • Almost there!
    • retrieveMetaObject improvements.
    • We will try to test it without the allow-thread patch to evaluate performance.
  • PYSIDE-813
    • we will keep PYSIDE-164 open until we find a solution that fixes both.
  • Starting to evaluate std::function compatibility with Shiboken.

5. March 2020

  • CI Update
    • Including Python 3.8
    • Maybe using alternatives to have many Python versions.
  • Priority bugs
    • PYSIDE-803
      • major changes in (caching)
      • still other minor patches to be merged.
      • allow-thread patch has a bug, maybe this can be detach from the snippets one.
    • PYSIDE-813
      • PYSIDE-164 appears again if we fix it,
      • Maybe a solution is to fix 164 in another way.
  • 5.15 feature status
  • Changes for Qt 6

27. February 2020

  • CI Updates
    • 5.12 cherry-picks
  • qApp
    • Deprecation message or alias (when using QtWidgets.qApp)
  • PYSIDE-803
    • Missing patches to be merged
      • Python 2.7 issues
      • allow-thread commit message (add a changelog)
      • second caching mechanism to be studied after we merge the first set of patches.
      • Third attempt after the stackless gilstate approach
    • Documentation
  • Python 3.8 testing is still being worked out

20. February 2020

  • CI Updates
    • Cherry-picking some changes to 5.12 to fix the virtualenv 20 issues.
    • macOS timeouts
    • possibility of merging simple changes directly.
  • qApp issues
    • Patches ready for review
  • PYSIDE-803
    • Patches needs some polishing
  • Testrunner improvements
    • stdout/stderr issues with ctest on windows
    • smart pointers tests crashing, due to qApp issues.
    • Python 3.8 is also giving problems (DLLs missing)
    • debug builds on windows does not work.
  • Shiboken documentation being reorganized
  • Starting testing Python 3.9

13. February 2020

  • CI updates
    • Windows package signing will be possible, hopefully soon.
  • Documentation updates
    • Example gallery
    • WebChannel example merged,
  • Python 3.8 changes on Windows are still being tackled.
  • Bugs
    • PYSIDE-803 status: A patch waiting for review is there, but we need to combine it with the other solutions we currently have. Still, there are some corner cases where the problem is not properly solved.
    • qApp issues to be solved, but we will remove the import features. qApp will remain as a built-in.
  • OKRS 1Q/2020

6. February 2020

  • CI status and issues with the Qt provisioning 5.12
    • 5.12.7 release will take more time to add new features.
    • 5.14 has some issues with OpenGLFunctions.
  • Documentation: Interest for the new shiboken2 documentation structure and usage of the ApiExtractor.
  • Python 3.8 compatibility with older branches.
  • Updates on PYSIDE-803 link
  • Suggestion about iterations a-la-python https://bugreports.qt.io/browse/PYSIDE-1216
  • Events
    • Qt World Summit 2020 Palm Springs
    • PyCon US

30. January 2020

  • 5.14.1 release rolling
  • Work on PYSIDE-1204
  • Work on PYSIDE-1191 PySide2 5.14 source now builds against Qt 5.12 as well
  • Further research on PYSIDE-803
    • full instrumentation of generated source for tracing,
    • discovery of new hooks to support. Still in flux.
  • Fixed some issues of Python 3.8 (most prominently warnings about implicit conversion to integers for QFlags), will be fixed in 5.14.2
  • qApp macro PYSIDE-1178 PYSIDE-1158 PYSIDE-1135 finally closed. One cleanup check in may follow.

23. January 2020

  • Fix for CI/macOS problem is in, but it requires some merges in Qt5. Until all required merges are done, we will use Qt5 5.14.1 with Qt For Python 5.14
  • Research on PYSIDE-803
  • Proposed an "until" attribute for typesystem files to make it possible to build Pyside 5.14 against Qt 5.12 PYSIDE-1195
  • Improved the view of compare app for PYSIDE-803
  • Analysis of PyQt5 and SIP implementation

16. January 2020

  • CI/macOS problems are being worked.
  • qApp fix waiting to be merged.
  • first attempts to tackle PYSIDE-803
  • Python 3.8 fix to old branches is required for distributions using 5.12 LTS like Conda.
  • Working on Q_ENUM support.
  • Viewer for PYSIDE-803 is ready to try. Please check out https://git.qt.io/playground/pyside-compare.git and give feedback.

9. January 2020

  • PYSIDE-803 needs to be tackled soon, it's critical, and we cannot carry that into Qt6.
  • Python 3.8.1 on Windows has some issues while building.
  • qApp macro changes discussion.
  • documentation updates are still pending.
  • with the release of 5.14 we have been fixing many details from uic's Python support.
  • designer's RUNPATH needed to be patched, waiting for approval,
  • A modular way of packing wheels is being studied.
  • Re-take the Python extensions for QtCreator project evaluation.

2019

2018