Qt for Python Development Notes: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(739 intermediate revisions by 15 users not shown)
Line 1: Line 1:
[[Category:QtForPython]]  
[[Category:Qt for Python]]
== 2018 ==


==== 17. May 2018 ====
==2025==
- updated icons/images for Qt for Python project


=== 27. March 2025 ===
* General
** A few comments on the state of the auto-generated documentation in our telegram group. We expect the community to help us by filing issues they find (per page) so we can try to address them.
* Infra & Releases
** Status of 6.8.3
*** Android NDK change is still updating. We might use some additional wheels for the release.
*** Flatpak update will be done as well.
** Status of 6.9.0
*** New NDK is already there, and the tests have succeed.
*** Branching 6.9.0 today/tomorrow after last changes
* Bugs & Features
** PYSIDE-3054 settrace bug was addressed, it was more important and difficult that we thought. Even some extra time was added to the import phase due to the recursion.
** Leaving the handling of Exception aside for shiboken.
** Type hints issues are still being addressed.
*** PYSIDE-3047 Debug option in Qt generates extra code in PySide, interfering with the wrappers. Function returns a qDebug rather than a QPolygon.
*** Other issues were addressed PYSIDE-3050 PYSIDE-3055 PYSIDE-3056 PYSIDE-3058
** Research on project structures to be more compatible with Xcode
** PYSIDE-3052 QMessageLogger and fix qInstallMessageHandler
** Bumping the nuitka version we use for pyside-deploy (2.6.8)
** Docs on debugging QtQuick app on QtCreator was missing a reference to create a QQmlDebuggingEnabler globally.
** qtpip - download android commercial wheel shows wrong wheel name on stdout- being fixed.


==== 03. May 2018 ====
=== 20. March 2025 ===
- coin
* General
  - 5.6 still blocked, 5.9/5.11/dev working
** PyPI organizations accepted Qt!
  - Win32 pip still on backlog
** We heard about https://wheelnext.dev/ it seems some ideas could be beneficial.
- documentation
* Infra & Releases
  - references to Shiboken being worked on
** A few issues in our CI in the last weeks (fixed now)
  - dot images finally working on https://doc-snapshots.qt.io/qtforpython/index.html
** Qt 6.8.3 new snapshot coming
  - various fixes to non-class related docs
** Qt 6.9.0 (internal rc2 to test)
- PEP updates
** We will move 'dev' to use Python 3.10+
  - integration attempts have revealed some issues with shiboken, private ctors/dtors
* Bugs & Features
  - one patchset series for PEP support and Heap Type changes pending
** Windows on ARM wheels are ready after a couple of issues (linking) were fixed.
- license updates
** PYSIDE-3049 - Missing plugin for qmllint (fixed)
- working on Python 2 & 3 type differences (avoiding developers having to deal with these differences)
** QML Bridges: Working on properties.
- Tab Browser example merged
** PYSIDE-3052 - QMessageLogger missing class (in progress)
** Working on merging the contributions on QtRemoteObjects
** PYSIDE-2854 - Support for [colocated objects|https://codereview.qt-project.org/c/pyside/pyside-setup/+/632241] in shiboken (structs issue, might support c++ unions)
** PYSIDE-3040 GTK Theming issue with PySide install
** Qt 6.10 adaption continues
** Speed of overriding methods (previously cached) - new fix is improving the performance, but duck-punching was not properly working.
*** Can this be excluded from the caching?
** The list of new improvements for type hints keeps growing (which is good!) so many issues has been solved.
** We might need to find a solution for the implicit conversions we do (like qdatetime/py_datetime)
** Discussion about Optional and pointer arguments that have a default value.
** Some property types (public class variables) are missing type information


==== 26. April 2018 ====
=== 13. March 2025 ===
- New icons for project in work
- 5.9 branch working  (5.11 branch is broken due to issues on the Qt side)
- snapshot tool for Windows broken (crashing) -> fix pending but blocked by CI
- in the mean time only mac and Linux snapshots working at the moment
- 5.6 branch broken as well as 5.9 changes for qt5.git need to be merged to 5.6 too
- delivery of 32bit Windows binaries not started
- tiny bug fixes and other types of cleanups (e.g. build scripts) left and right
- General replacement of Pyside name against Qt for Python (module name remains as Pyside)
- APIExtractor documentation still being merged to git
- style sheet issues being addressed
- QtWebEngineCore bindings finally merged
- PEP work ongoing (and coin to work)


==== 19. April 2018 ====
* General
- COIN finally back in working shape
** QtCS: We need to submit talks in case we want to attend.
- Further fixes for documentation, module pages, experimentally tried to show in Qt Assistant
** Tomorrow Python 3.14a6 will be released https://peps.python.org/pep-0745/
- Tab Browser example further improved
* Infra & Releases
- Qt for Python blog posts being worked on
** Windows on ARM research continues and looks good! managed to fix an issue, but a new issues was found on samplebinding. The issue might be related to missing OpenGL.
- Continued working on WebEngine issues
** 6.9.0rc might be released tomorrow, which means PySide6 FF will be due.
- Some investigation and preparations to make WebEngine apps work with PyInstaller (very early phase, still doesn't work)
* Bugs & Features
- Pending patch for QtWebEngineCore bindings
** Many new type hints bugs being reported :)
- Installation adjustments for standalone builds on Windows
** Smart pointers exclusion issues fixed (shiboken)
- Heap types are complete. Starting integration with PEP 384.
** Designer and Linguist tools fixes (External)
- Finished the integration between ApiExtractor and Shiboken documentation.
** Helping the remoteobject contributions to work better.
- Worked on a couple of blog posts.
** Documentation checks and 6.10 adaption.
- Wiki structure and started to write the Tutorials
** https://bugreports.qt.io/browse/PYSIDE-2221 Going back to the free threaded Python topic in PySide
*** Lots of changes since the previous attempt
** https://bugreports.qt.io/browse/PYSIDE-3012 Kept working on the pep8 compatibility for type hints issues
** https://bugreports.qt.io/browse/PYSIDE-3034 trying to figure out to get type information from public variables
** https://bugreports.qt.io/browse/PYSIDE-3046 fixing type issues
** Re-Starting research on iOS compatibility
** QML Bridges: Slots registration is working now! new tests are being written.


==== 12. April 2018 ====
=== 6. March 2025 ===
- Getting Started guide under works by doc engineer
- focus on fixing coin on Mac & RedHat 7.4 (looks promising so far)
- shiboken documentation and diagrams being updated
  - old and unused docs dir shall be cleaned out
- Tab Browser example improved
- License page generated based on attribution files
- lots of discussion when to release Qt for Python TP
  - after Qt 5.11 release (scheduled for 31.5.)
  - likely to be mid June (stay tuned)
- WebEngine issues
  - needs updated qt.conf files to be deployed for apps
- Heap types (work in progress)
- still more work in pipeline to get code PEP 384 ready (Heap types are prerequisite)
- Qt for Python blog posts being worked on


==== 5. April 2018 ====
* General
- first doc snapshot is up and running: https://doc-snapshots.qt.io/qtforpython/
** Jaime's internal presentation will be next Monday at 11am
- more work to be done to automate generation of snapshots
** QtCS registration is up.
- briefly talked about technical blog post opportunities
** Discussion on IPC options for Qt developers.
- pdb files from Windows wheels removed (reducing the wheel size)
* Infra & Releases
  - improving the tab browser example
** 6.9 Qt for Python FF happening next week.
- coin currently not accepting changes
** Windows on ARM deployment test failing.
  - currently lots of pending patches start to create backlog
* Bugs & Features
- Heap type taking longer than expected
** Remote object contributions are going well, and we might merge them for 6.9
- qApp macro reference leaks finally resolved
** Binary size reduction research continued, but it seems we have reached the reduction we can, without touching the C++ side of our bindings.
- quite a few formatting changes to enforce a common coding style
** PYSIDE-3012 Type hints issues were addressed (typing.Sequence -> typing.Collection) even if it is a simple change in theory, to change it internally and for our generation it took a lot of time.
- lots of smaller fixes
*** Removing object-inheritance in the pyi files
*** White-space around equal operators issue (default parameters)
** Update Widget Gallery example
** Changed to adapt std::chrono patches in shiboken (identify overloads and choose the better option)
** Cleaning up some bug reports, metamethod connection issue fixed.
** Addressing some coverity issues for Designer
** Started 6.10 adaption.
** QML Next works continues.
** Changes in the build system scripts are still in progress, some stuff is broken when used, but it's going in a good direction.
** Finalizing the pyside6-project changes to adapt the pyproject.toml changes.
** Addressing new found QtCreator issues with the pyproject.toml compatibility.


==== 29. March 2018 ====
=== 27. February 2025 ===
- skipped due to Easter holidays
* General
** Windows on ARM improving
* Bugs & Features
** PYSIDE-2701 Size reduction, investigating removing redundant overloads
** PYSIDE-2701 Size reduction, trying wrapper folding, needs massive reordering
** PYSIDE-3012 replacement of typing.Sequence by collections.abc.Sequence
*** Identified incompatibility with Python < 3.9.8 and Python < 3.10.1, fixed by small patch
*** First change finally done, needs series of further changes
** 6.10 adaption continues
** PYSIDE 2942 Slot type annotation fix
** QTBUG-132266 Checked the code on macOS that the user uploaded, no issues were found related to PySide or macOS.


==== 22. March 2018 ====
=== 20. February 2025 ===
- Release process (do we follow Qt?)
* General
  - Release manager provides packages
** QtWS possible participation
  - RTA testing to be setup -> for each package we run RTA
** QtCS has a priority of bringing more external contributors
  - Request to be put on mailing list
* Infra & Releases
  - Current Test setup proposal
** 6.9 RC February 28th (maybe postponed)
    - Win10 (Python 3.6)
** Windows on ARM test cases failing due to mypy fast cache (requires rust toolchain, that's currently missing from the CI). static libclang doesn't work on ARM builds (but does in x86_64).
    - Linux (Python 3.6/2.7)
** RTA trials continue, possibility to use qtpip
    - Mac (Python 3.6/2.7)
* Bugs & Features
  - To be defined a test set (//TODO)
** PYSIDE-2701 Size reduction for virtual functions patch was merged
  - Testing information to be collected in wiki
** PYSIDE-3002 painted virtual functions solved (even though we had our own opinion about performance)
- Documentation
** 3020 SignalInstance disconnect issue fixed
  - QML advanced tutorial documentation updated
** Templates/snippets cleanup in the typesystem.
  - Landing page in the works
** 6.10 adaption continues
  - snapshot still delayed by other qdoc bugs
** QtCreator toml changes:
  - style sheet update considered
*** psyide6-project adaption to the latest changed related
  - so far only dealt with class docs, started to include unrelated doc pages
** QtDS changes postponed (to be available in QtDS 4.8)
- snapshot testing (angle & webengine not properly packaged on Windows)
** PYSIDE-3017 QSerialBus overload order issue was fixed
- enum support improved (dealing with scoped enums and enum values)
** PYSIDE-3012 Still addressing issues (CI currently failing)
- general bugfixing to increase stability and address mem leaks
** qtqa improving the wheel testing process.
- Talks to PyData submitted
** Brainstorming a better approach for QML Next
- Qt Charts examples ported
** Finishing the folding patches, they don't make a lot of sense at the moment due to previous changes (being added into shiboken)
- Proper support for QFlags being worked on
- [https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595] fixed
- [https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595] first heap type protoype under review proving that concept works
  - [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560] depends on PYSIDE-595
- CI side
  - coin did Python updates which temporarily broke Linux wheels
  - briefly discussed manylinux request on mailing list (Qt forms bottom line, no point to extend beyond scope of Qt)
  - final list of wheels for release (win, linux, mac) x 2 (2.7 & 3.x Python)


==== 15. March 2018 ====
- Fix to create 3.6 Linux wheels under review.
- Fix scriptableapplication build on Windows, and other small bugs.
- Two QtCharts examples were ported and abstracts were written to submit PyData talks
- Updating the QML advanced tutorial and adding index.rst and gettingstarted.rst
- Tried the wheel pkgs for python 27 on Linux. Works OK except the webengine example, which gives random crashes.
- Docs: [https://bugreports.qt.io/browse/PYSIDE-620 PYSIDE-620 Shadow build issue] fixed, fixed usage of deprecated Sphinx API,
- Continued on [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560], currently  Windows problem with Linkage
- Debugging on [https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595], final stages
- Fixed [https://bugreports.qt.io/browse/PYSIDE-258 PYSIDE-258]


==== 08. March 2018 ====
=== 13. February 2025 ===
- msvcrt.dll to be shipped on Windows
* General
- wheel snapshots are automatically generated
** Did you know Shiboken translates into "Death Sword"? 死某剣
  - start with public availability under http://download.qt.io/snapshots/ci/
** QtCS happening after QtWS in Munich in early May.
  - snapshots to public pypi server under discussions
** Qt Design Studio integration (internal presentation) with Python to be prepared.
- discussion on how to increase value of official pyside mailing list http://lists.qt-project.org/mailman/listinfo/pyside
* Infra & Releases
- looking at build issues on Windows (improving error handling)
** Windows on ARM research continues.
- Participation in Python User Group meeting in Berlin (https://www.meetup.com/Python-Users-Berlin-PUB/events/xhqwhpyxfblb/)
** QtDS wheels to be updated for the new release
- [https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595] - Heap Type conversions ongoing
** 6.9.0 RC by the end of the February.
  - test bed created for easier development
** RTA testing initiative to be restart
- [https://bugreports.qt.io/browse/PYSIDE-363 Documentation]
** Evaluating scikit-core-build for replacing build_scripts/
  -> Managed to make libxml, libxsl an optional dependency falling back to QtXmlPatterns (despite [https://bugreports.qt.io/browse/QTBUG-66925 QTBUG-66925])
* Bugs & Features
  -> Small fixes to doc modifications
** Flatpak issue was solved (cleanup)
  -> Fix class inheritance diagrams for nested classes
** Brainstorming ideas for QML Next (preparing internal presentation)
** Android wheel names to be adapted https://packaging.python.org/en/latest/specifications/platform-compatibility-tags/#android
** Qt Creator finishing .toml support for Python Projects.
** Qt DS Python changes ready to be merged
*** Tutorial changes to be prepared
** Type hints heuristic evaluation in order to address newly found issues related to overloads with similar shape.
** Handling of value-types in shiboken (refactoring, new features and doc)
** PYSIDE-3005 OpenGL issues were fixed
** PYSIDE-3013 Font issue was fixed
** PYSIDE-3015 OpcUA support bug fixed
** PYSIDE-3014 virtual function on QSpinBox issue fixed
** 6.9 adaption patches
*** Found newly moc changes were breaking our enums
** Size Reduction
*** hashing functions to re-use them.
*** changing the policy to use absolute size measure (sizebench)
*** Removing a few things from the folding patch, in order to merge it
** PYSIDE-2997 and PYSIDE-3003 type hints issues were solved. A couple are still open.


==== 01. March 2018 ====
=== 6. February 2025 ===
- automatic snapshot process almost in place (pending reviews) (RTA to follow)
* General
- general bug fixing (including build and version problems)
** We went to FOSDEM and meet many PySide users!
- most community Pyside1 pages point to official Pyside 2 (Qt for Python) wiki pages
** Commercial / LTS naming on the Installer.
- [https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595] - Heap Type conversions ongoing
* Infra & Releases
- documentation improving
** Reviewing our branching policies. There is interest in branching pyside-setup sooner.
  -> class diagrams being generated
** We might need to move the Android wheels to PyPI (Probably from 6.9 on)
  -> missing links and references
** 6.8.2.1 release is planned in order to fix the missing DLLs in Windows (MSVC)
  -> dependencies to qdoc bugs
*** cheery pick is missing for 5.15
  -> snapshot process in works
** PySide6_DS 4.7 to be released in the next couple of weeks.
- added support for scoped enums in pyside
* Bugs & Features
- Important things discussed:
** Adding TOML support for Python projects in QtCreator
  - PySide2 versioning (current proposal WIP patch at https://codereview.qt-project.org/#/c/221767/)
** TypeHints new reports, trying to get an idea of what's causing the errors
    - Do official releases follow Qt branch names? -
** Issues in Flatpak: updating version, checking a cleanup issue. Addressing dependencies issues for optional packages.
      -> yes (minor release of Pyside is bound to same minor release of Qt
** QtQA internal scripting: Adapting an automatic wheel download.
      -> patch level version may differ
** Size reduction
    - Will we have snapshots, and if so, will they be uploaded to pip? How will we handle snapshot versions?
*** Move virtual function overrides. Only generated on the base classes.
      -> tentative yes, if public pip server supports snapshots Pyside should be good citizen
*** Discovered and fixed a few multiple inheritance with shiboken
    - alpha / beta / RC versioning?
** Snippets translation tool: Trying to add a feature to use fully qualified enums.
      -> Pyside should follow the Qt schema
** clang-tidy warnings were fixes
    - Probably need to take into account PEPs for versions pushed to Pypi.
** Handling value types on non-default constructors (inspired by 6.9 changes)
    - Shiboken / PySide2 versions in sync?
** Discussion on moving away out internal building process to scikit-build
      -> yes, they should be in sync
** Size reduction (folding approach): To publish first results soon.
    - Will we specify a version for 5.6 branch?
** Supporting team member with pyi session to understand the internal mechanism.
      -> yes, but no packages being made
** Ideas from the size reduction research were implemented
    - Are we sticking to the package name PySide2, but follow Qt 5.x versions as PySide2 versions?
** Changing the benchmark code for the size reduction (which might not include the new changes to shiboken)
      -> Pyside2_5.11.0 as in https://codereview.qt-project.org/#/c/221767/
  - Do we want to deploy msvcrt dlls into Windows packages?
    -> needs more research - is it really needed ?
  - Do we want to ship debug symbols for Qt inside the PySide2 packages?
    -> not for now
  - Do we want to ship debug Qt shared libraries for macOS packages? (not possible on Windows, not applicable on Linux afaik).
    -> not for now
  - How will the pip upload process look like? Manual uploads? Who takes care of it?
    -> Qt release team will take care of it
  - Current branching policies:
    -> 5.6 branch stops being merged into 5.9 (after pending patches have merged) -> cherry-pick mode
    -> 5.9 is base line for patches and being forward merged to 5.11
    -> no packages from 5.9 & 5.6 (interested parties need to get it from git)
    -> 5.11 becomes branch for first TP
    -> dev is feature development
    -> all first TP release related patches go to 5.9 (and 5.11 subsequently)


==== 22. February 2018 ====
=== 30. January 2025 ===
- dev branch is still/again broken in CI, seems like pyside issues
- changes to create automatic snapshots out of CI is still under review
- Numerous small fixes to the [https://bugreports.qt.io/browse/PYSIDE-363 doc] generation, significantly bringing down the number of documentation warnings
- Massaged build rules to improve built packages
  - Removed unnecessary _utils.py file [https://bugreports.qt.io/browse/PYSIDE-600 PYSIDE-600]
  - 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]
  - Finally got libclang to be deployed into packages
  - 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]
  - 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]
  - Fixed rpath handling for QtWebEngineProcess when creating standalone packages on macOS [https://bugreports.qt.io/browse/PYSIDE-605 PYSIDE-605]
- Added CMake build rules for scriptable application example [https://bugreports.qt.io/browse/PYSIDE-597 PYSIDE-597]
- Investigated and fixed a heap corruption bug in a test that caused constant crashes on macOS CI runs
- Reduced number of warnings when running shiboken to create user bindings (like scriptable application example) [https://bugreports.qt.io/browse/PYSIDE-587 PYSIDE-587]
- [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.
- Havent's merge [https://codereview.qt-project.org/#/c/220083/ this new patch] because we should be 200% sure it's properly working.
- Working on a few bugs [https://bugreports.qt.io/browse/PYSIDE-106 PYSIDE-106] [https://bugreports.qt.io/browse/PYSIDE-570 PYSIDE-570]
- 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.


==== 15. February 2018 ====
* General
- CI broken, 5.6 & dev branch broken, 5.9 just got working again
* Infra & Releases
- 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)
** Preparing 6.8.2
- more modules added to doc, qt3d & qtquick has some special handling
* Bugs & Features
- snippet work ongoing
** Size reduction [https://bugreports.qt.io/browse/PYSIDE-2701 PYSIDE-2701] : Implemented code reuse for Python overrides of virtual functions
- snapshot generation on the agenda
** QtPythonScripting: continue working on multiple inheritance, added more widgets
- lots of bug fixing e.g.: [https://bugreports.qt.io/browse/PYSIDE-104 PYSIDE-104]
** Size reduction: PYSIDE-2701 Folding progress: We can now combine multiple foldings of the same function. This will bring some more reduction.
- [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560]
** Simplebrowser example updated
** adding imageviewer docs
=== 23. January 2025 ===


==== 8. February 2018 ====
* General
- Looking through previous EuroPython talks to write a proposal for this year.         
** [https://invent.kde.org/frameworks/kconfig/-/jobs/2497118 KDE testing Qt betas and snapshots]
- Working on a few bugs (fixed a couple related to objects references),               
*** Should we update our Branching policy?
  - that sadly will open new issues with memory management. A further analysis on this matter could improve the current memory leaks on PySide.                         
*** Our branching policy:
- Trying to "organise" a little the typesystem XML files.                             
**** We branch briefly after API Review is done in qt meta repo.
- 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.
** Yocto libclang issue - https://codereview.qt-project.org/c/pyside/pyside-setup/+/609352
- Merged a few build related changes in 5.6
* Infra & Releases
  - Pending change for [https://bugreports.qt.io/browse/PYSIDE-593 PYSIDE-593]
** Windows on ARM configuration testing.
  - Pending change for [https://bugreports.qt.io/browse/PYSIDE-605 PYSIDE-605]
** 6.8.2 scheduled release next week, and branching will happen today.
  - Merged changes for [https://bugreports.qt.io/browse/PYSIDE-603 PYSIDE-603] and [https://bugreports.qt.io/browse/PYSIDE-604 PYSIDE-604]
* Bugs & Features
- Investigated and attached minimal reproducible example for [https://bugreports.qt.io/browse/PYSIDE-585 PYSIDE-585]
** QtPythonScripting: continue working on Stable ABI support and multiple inheritance
- Investigated some macOS build related aspects for package release
** [ext] 6.9 Designer release issues with macOS drag and drop + bug fixing
- 5.6 CI is unblocked, but 5.9 CI is blocked due to qtbase issues (version bumping)
** PYSIDE-2990 Slot Executed in Signal's Thread Even With Auto & QueuedConnection
- [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560] waiting for view
*** People is getting the documentation from an outdated wiki page, which is causing new reports.
- [https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595] work ongoing, not ready yet
*** Wiki will be updated.
- [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.
** Size reduction: we generate a lot of code for parsing keyword arguments. The code was moved to libshiboken and the size was reduced 3%
- Problems with Qt3D due to refactoring of Qt3Dextras in 5.10. Pushed  [https://codereview.qt-project.org/#/c/219105/ patch] suggestion.
*** Optimization reviews: it seems it's only the virtual functions, but not the actual bindings.
** Size reduction: Windows is giving some issues for special characters, which seems to be also present in Linux.
** Cross compiling and creating wheels with the new JNI classes bindings. Trying to test them in an emulator, found other issues.
** pyside6-deploy/project and DS changes integrating, hopefully they will be merged today \o/
** DS-only changes are still in review.
** TOML integration - continue research on adding new format for python projects
** QtGraphWidgets issue with yocto build was fixed.


==== 1. February 2018 ====
=== 16. January 2025 ===
- Continued work on documentation [https://bugreports.qt.io/browse/PYSIDE-363 PYSIDE-363], fixed static pages, add more modules, fixed parameters to qdoc, images
- The GettingStarted wiki is getting better, besides a cleaning it a bit
  - moved the topics around to have guidelines by supported platform (''a la Qt'')
  - have received feedback and trying to add more information
- Addressed bugs:
  - [https://bugreports.qt.io/browse/PYSIDE-34 PYSIDE-34]
  - [https://bugreports.qt.io/browse/PYSIDE-264 PYSIDE-264]
  - cleaning a bit Shiboken's XML files.
  - [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560]
    - ported to 5.9, extended to 18 header files
    - solved unicode problem
    - reduced the patches to be minimal (avoid many #ifdef's, use a verbose macro name if possible)
    - 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.
  - [https://bugreports.qt.io/browse/PYSIDE-595 PYSIDE-595]
    - Started experimenting
    - 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.
- 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 ====
* General
- Pyside not renamed
** Highly probable that one of us will go to FOSDEM to help with the Qt Project stand! so if you /reader/ are going, drop by and say hi!
- Releasing preparation
* Infra & Releases
  - pip packages created by coin
** 6.8.2 will be released on 23th January so far, so we expect providing the wheels in the following days.
  - Automated release testing (RTA) (installing pip, launching an example)
** 3.13 on the CI still on-going.
  - final selection of release package targets to be define closer to release (depending on current stable ABI work)
** 6.5.4 OSS released
- Investigation doc issues when using prefix & shadow builds
* Bugs & Features
- Need to identify prime demos/examples
** Discussion about QJni* bindings when cross compiling.
- Started to rework [[PySide2 GettingStarted|Getting Started Guide]] wiki
*** It did built (and installed) for aarch64 and x86_64 but armv7a will be tried later on.
- Addressed cmake build issues
*** The main issue with this story was that it was bindings only for cross compiled pyside
- Handling libICU issues (causing linker issues when importing QtCore)
** Exploring toml compatibilities within QtCreator
- Continued work on [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560]
** DS patches still needs review.
** Binary size work continues
*** 17% reduction so far, and this could be included in the future-features list.
*** Once is ready, we might provide an option to disable it to go back to the more readable wrapper code.
*** We might evaluate a template approach once the solution is out, to avoid maintaining regexes.
** Remote Object reviews ready in order to merge changes (only a few details)
** Qt Python Scripting
*** Multiple inheritance is not supported yet.
*** REPL function to help development
*** Research on Limited API usage.
*** find_python macro in 3.26 allow to find the stable abi
** docstring changes in order to expose them as docstring per methods.
*** some experiment to add it to the pyi files, but it doesn't show.


==== 18. January 2018 ====
=== 09. January 2025 ===
  - macOS framework fix (should ignore qt4 system headers)
  - another patch on top to fix OpenGL integer types on mac / Linux (GLuint64, GLint64)
  - 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
  - Completed move of examples from pyside-examples.git to pyside-setup
  - added additional OpenGL2 core example
  - fixed testrunner (these silently failed since forever) https://codereview.qt-project.org/#/c/216732/
  - fixed issues whereby wrong QObject ctors were selected
  - removed webkit from Pyside2 build 
  - 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 ====
* General
- multi pyside packages (not easy to do)
** FOSDEM 2025: Qt got a stand!
  - unlikely to achieve until TP
** Internal Hackathon going on.
  - a package per python release (3.4, 3.5, 3.6, 2.7)
* Infra & Releases
  - package per platform (win 32bit|64bit, mac, linux)
** https://download.qt.io/official_releases/QtForPython/ got restructured and it's now very tidy
  - long term task to convert to reduced Python API (to support multi 3x packages)
** Preparing 6.8.2
  => have to cut some targets: one 3x and 2.7 release
** 6.8.1.1 Windows and Linux wheels were uploaded for consistency thanks to user-reports when uploading only the 6.8.1.1 on macOS due to a missing module
  -> create doc howto to encourage custom builds for not covered platform combo
** Tests with 3.13 on the CI
  -> do we need commercial for release
* Bugs & Features
- pysinstaller is an installer
** [https://bugreports.qt.io/browse/PYSIDE-2966 PYSIDE-2966] Disabled instantiating non-instantiable classes
  -> deployqt tool not necessary
** [https://bugreports.qt.io/browse/PYSIDE-1735 PYSIDE-1735] Examples and tests were ported to use fully qualified enumerations
  -> documentation required stating the option
** Python Scripting continues (enable adding __repr__ functions)
- rename import options
** Discussion about QJni* bindings when cross compiling.
  - rename via alias possible
*** We might try a few new configurations for adding this bindings.
  -> still an issue when looking up particular types but probably manageable 
** Tutorial for Boot2Qt and PySide apps deployment
  - renaming option: Qt4Pyton, QtPy, QtPython, Python4Qt, Qt
** Doc changes: adding comments for using uv
- example shift
** QML Next: still working on improved decorators for a smoother integration
  - https://codereview.qt-project.org/#/c/215900/
** Qt Remote Objects: Big set of patches by external contributor
- Basics for doc generation toolchain
** Binary size reduction work continues with new ideas from other projects: folding, string handling, renaming, etc.
- Issues where cmake picks up platform Qt references where it should use a Qt custom install
** Yocto builds issues with LLVM still not solved.
- 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 ====
==2024==
- multi pyside packages (not easy to do)
- 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 ==
*[[Qt for Python Development Notes 2024]]


<div class="mw-collapsible mw-collapsed" style="overflow:auto;">
==2023==


==== 21. December 2017 ====
*[[Qt for Python Development Notes 2023]]
- Issues building for Windows for Python 2 and 3 (on coin)
- discussing potential pyside demo/example for RTA purposes
- Continued work on macOS / Qt 4 header issues, progress is there
  - breaks GL signature test on Linux, needs further investigation
- Investigated PyInstaller (potential option to deploy apps written with Pyside)
  - seems to work almost out-of-the-box for deploying PySide apps
- Investigated building one package compatible with multiple Python 3.x minor versions
  - not possible currently, will require a lot of work, possibly not feasible
  => we need to build 3.4,3.5,3.6 * win, linux, mac packages = 9 packages
  => 3 more for each platform and Python 2.x
  => commercial packages?
- lots of discussions and fixing of doc tool chain (qdoc in dev currently broken)
  - adding documentation has begun in earnest
- continued work on PYSIDE-578


==== 7. December 2017 ====
==2022==
- pip wheel installation
  - adding support for simultaneously python 2 and 3 builds
  - open issues: test installation towards multi python 3 versions
  - delivery channel for Pyside binaries (pip server? local install from qt account download?)
- investigate options to have sth like pyinstallqt (pysinstaller is a possibility)
- final keyword support by shiboken
- Qt3D bindings patch close to completion - > requires some Qt changes in 5.9.4 or later Qt
- fixing pyside build issues when encountering Qt 4 headers on macOS
- PYSIDE-578 (testing procedure/testrunner) -> adds heuristic to adapt to failure rates (flakiness handling)
  - concerns that running all tests 5 times adds too much load on the CI (test runs needed)


==== 30. November 2017 ====
*[[Qt for Python Development Notes 2022]]
- packaging related coin changes
- last weeks merges between 5.6 and 5.9+ blocking coin have been fixed (in particular on RHEL)
  - 5.9 + 5.6 are passing, dev has some private Qt changes which will affect pyside/dev
- lots of coin infrastructure issues
- RTA test wheels added (install and launch single example)
- crash bugs in 5.6 branch reported but not details known yet (waiting for more details)
- some discussion what changes should be put to 5.6 vs 5.9 branch
- Qt3D bindings started
  - some changes in qt3d/5.9 required)
  - 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 ====
==2021==
- 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 ====
*[[Qt for Python Development Notes 2021]]
- Build system cleanup. It is now possible to build only a subset of Qt modules per cmd line option
  -  this is not complete and may need further patches
- Added QAxContainer, more classes from 5.10
- Preparing to add Qt3D
- Removed flaky test
- further research on how pip wheels might be used for Pyside
  - seems to work well on win & macOS
  - problems on Linux related to libICU (or in general due to different system libraries)
- 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 ====
==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 ====
*[[Qt for Python Development Notes 2020]]
- Releasing:
  - continued work on macOS installer
  - binaries must be patched during the install from repo (rpath setting)
  - adopting the scripts from Qt for Pyside
  - made pip install work on Mac -> would be alternative to online installer approach
    - 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 ====
==2019==
- 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 ====
*[[Qt for Python Development Notes 2019]]
- Discuss open Pyside 2 release & documentation
- Release packaging suggestion
  - Qt for Python installed via Qt installer and python scripts pointed to module via PYTHON_PATH
  - create test online repository for Qt installer
  - follow up how this Pyside installation approach might impact deployment of Python apps using Qt for Python
  - Linux distros shipping Pyside? (not sure yet either)
- coin
  - breakage in CI provisioning due to competing Python binaries coming from MSVC 2017
  - coin template needs updating
- [https://bugreports.qt.io/browse/PYSIDE-571 PYSIDE-571] work progressing (ready for review)
- lots of fixes in Pyside dev branch and
- feedback from Qt World Summit:
  - is Pyside on Android and iOS?
  - iOS probably out since platform cannot have interpreted code
  - 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 ====
==2018==
- no update due to Qt World Summit 2017


==== 05. October 2017 ====
*[[Qt for Python Development Notes 2018]]
- Qt DataVisualization port has finished including an example
- Coin no progress due to pending Qt 5.9.2 release
- webxml support being implemented inside qdoc (beginning of the pyside documentation toolchain)
 
==== 28. September 2017 ====
- 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 ====
 
- Prototyping and exploring of Pyside packaging options
- [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 ====
- Coin
  - 5.6 testing is back online (5.9 target unblocking pending a merge)
  - Packaging of Pyside started to become a discussion topic
    - Standard PIP deployment
    - Separate delivery via the usual Qt account channel
- void* support has a pending patch (https://codereview.qt-project.org/#/c/205124/ and related example https://codereview.qt-project.org/#/c/205272/)
- Documentation work ongoing
  - WebXML support was added to qdoc - see [https://bugreports.qt.io/browse/PYSIDE-363 PYSIDE-363]
  - inputting the resulting WebXML to shiboken gave promising results
  - Qt Creator gain ability to fold away Python license headers
- Signature patch (https://codereview.qt-project.org/#/c/198654/)
 
==== 7. September 2017 ====
- 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 ====
- Coin 5.9 provisioning is in place, but there are some issues with paths to tools which are being addressed
- Build issue on Windows 10 5.9 branch, addressed by patch in review https://codereview.qt-project.org/#/c/203406/
- Fix to macOS build when old Qt 4.8 is present, addressed by patch https://codereview.qt-project.org/#/c/203313/
- [https://bugreports.qt.io/browse/PYSIDE-516 PYSIDE-516] progress on bringing in more of the QOpenGL classes
- [https://bugreports.qt.io/browse/PYSIDE-560 PYSIDE-560] stable ABI was investigated, decision is required
- [https://bugreports.qt.io/browse/PYSIDE-510 PYSIDE-510] finalizing license modifications
- [https://bugreports.qt.io/browse/PYSIDE-156 PYSIDE-156] ongoing implementation for fixing qApp crashes
- [https://bugreports.qt.io/browse/PYSIDE-552 PYSIDE-552] in process of being merged
- [https://bugreports.qt.io/browse/PYSIDE-562 PYSIDE-562] pending patch
- [https://bugreports.qt.io/browse/PYSIDE-563 PYSIDE-563] in process of being merged
- PySide 2 presentation being prepared for Qt World Summit 2017
 
==== 17. August 2017 ====
- 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 ====
- holiday time is hampering project at the moment -  not much progress
- CI changesin Qt affected Pyside project such that focus was on different CI matters
- [https://bugreports.qt.io/browse/PYSIDE-557 PYSIDE-557] being addressed
- some very minor issues were fixed
 
==== 03. August 2017 ====
- 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 ====
- Fix for [https://bugreports.qt.io/browse/PYSIDE-331 PYSIDE-331] causes lots crashes in auto tests
  -> more investigation ongoing
- coin
  - since 5.6 is now enforced by Qt CI the focus shifted to the 5.9 branch of Pyside
  - still encountering build issues on 5.6 though
  - cmake upgrade for macOS 10.10
  - missing virtual env for macOS 10.12 being deployed
  - msvc 2013 being removed from CI targets
  - clang on OpenSuSE deployment ongoing
  - lots of effort went into debugging the above Coin issues
- numpy support for 2d array feature development progressing ([https://bugreports.qt.io/browse/PYSIDE-354 PYSIDE-354])
 
==== 20. July 2017 ====
- 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 ====
- coin
  - Production coin was updated today and all fixes are finally executed
  - 5.6
  - macOS 10.11 machines have Python 2.6, which causes test script to fail due its usage of a
          module added in 2.7. Investigation in progress on the best way to fix this.
  - build failure with Windows 8.1 (msvc2013-x86)
  - 5.9
  - macOS 10.12 missing virtual env (https://codereview.qt-project.org/200006)
  - Rest Linux/macOS configs are failing various build issues
  - dev is still pending for qt5 merge from 5.9 
- [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 ====
- 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 ====
- building pyside on Win with debug and non-debug
- QSSL* classes do not build on macOS & Windows (patch in progress)
- dll name handling work finished (build system issues were addressed)
- PYSIDE-531 discussions
- coin
  - followup from 18 May (windows issues in coin)
  - test runner changes being merged should address this
  - new regression on macOS targets though
  - 5.9 issues due to clang continue to exist (will be addressed after 5.6 is enforced)
 
==== 15. June 2017 ====
- dll name handling fixed across the platforms (e.g. pkgconfig handling)
- PYSIDE-500 fixed
- PYSIDE-331 is still not done (in parts a module by module fix is required)
- PYSIDE-510 ongoing
- no further progress on coin
- Getting started guide has been updated dealing with Qt 5.6 and Qt 5.9 based Pyside builds
- scriptable Pyside example been developed to demonstrate SDK-like usage of Pyside
- lots of small infrastructure changes/fixes
 
==== 8. June 2017 ====
- Proposed solution for PYSIDE-500
- Further work on example for PYSIDE-526, work on shiboken2 command line handling to ease usage with qmake
- Updated Getting started Wiki
- Introspection work continued (PYSIDE-510)
 
==== 1. June 2017 ====
- PYSIDE-500
- https://wiki.qt.io/PySide2_GettingStarted needs a serious cleanup
  - 5.6 vs 5.9 differences not explained
  - specify exact version matching conditions
- pyside repo merge completed
  - Coin changes required to catchup - > recent CI issues have caused delay
- 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 ====
- Coin
  - Win nodes didn't run the cleanup functions -> test failures due to artifacts -> no solution yet
  - Clang issues persist and this must be addressed in the broader scope of Qt/qdoc depending on libclang too
    -> until this point in time the setup is a manual one for pyside/5.9+
- merge of psyide repositories -> no objections against the plan in the community
  -> merge will happen in the next few days (pyside.git, pyside-setup.git and shiboken.git become one repo)
  -> examples, wiki and tools will remain as they are
- QOpenGL* porting continuing
- 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 ====
- 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.
- 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 ====
- 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 ====
- 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>
 
=== Backlog ===
 
The list below represents some short term targets and long term ideas for Pyside2 development. There is no guarantee that this will happen as written down. It is meant as a short reminder and idea collection for future development. In the long term this list is likely to move to https://bugreports.qt.io/browse/PYSIDE.
 
# First time with Pyside (Document how to get started on this wiki)
# Testing Infrastructure
## What has been done so far?
## Qt CI support ([https://bugreports.qt.io/browse/PYSIDE-431 PYSIDE-431])
### make test
### cmake based build system (all repos)
### pip installable Pyside
#### CI has to setup virtual Python environment
#### Use pip to install/build Pyside (release bundling)
 
# Future changes to PySide
## Gaps (modules & API)
### Identify the extent of the gaps by porting existing examples from Qt4 to Qt5 (done)
### Plugin system (in what form or shape do we need it is uncertain - some failing tests exist already)
### Prepare a summary of gaps for other modules
## Fundamental Architecture changes
### Shiboken
#### Clang support ([https://bugreports.qt.io/browse/PYSIDE-323 PYSIDE-323])
### QtQML support ([https://bugreports.qt.io/browse/PYSIDE-355 PYSIDE-355])
## MyPy (type annotation - fully typed Python API)
## General Python features and their adoption in PySide (e.g. Async I/O)
## Creator and tooling
### Fix QtC debugger to understand Python/C++ mixed internals
## Documentation generation
## Deployment of apps
## Debugging support
 
# Must have tasks for first release
## Packaging (e.g. pip deployment? )
## Clarify Installer story
## Documentation
## Product placement decisions
### Licensing
### Naming
### etc
## Complete CI coverage

Revision as of 10:02, 27 March 2025


2025

27. March 2025

  • General
    • A few comments on the state of the auto-generated documentation in our telegram group. We expect the community to help us by filing issues they find (per page) so we can try to address them.
  • Infra & Releases
    • Status of 6.8.3
      • Android NDK change is still updating. We might use some additional wheels for the release.
      • Flatpak update will be done as well.
    • Status of 6.9.0
      • New NDK is already there, and the tests have succeed.
      • Branching 6.9.0 today/tomorrow after last changes
  • Bugs & Features
    • PYSIDE-3054 settrace bug was addressed, it was more important and difficult that we thought. Even some extra time was added to the import phase due to the recursion.
    • Leaving the handling of Exception aside for shiboken.
    • Type hints issues are still being addressed.
      • PYSIDE-3047 Debug option in Qt generates extra code in PySide, interfering with the wrappers. Function returns a qDebug rather than a QPolygon.
      • Other issues were addressed PYSIDE-3050 PYSIDE-3055 PYSIDE-3056 PYSIDE-3058
    • Research on project structures to be more compatible with Xcode
    • PYSIDE-3052 QMessageLogger and fix qInstallMessageHandler
    • Bumping the nuitka version we use for pyside-deploy (2.6.8)
    • Docs on debugging QtQuick app on QtCreator was missing a reference to create a QQmlDebuggingEnabler globally.
    • qtpip - download android commercial wheel shows wrong wheel name on stdout- being fixed.

20. March 2025

  • General
    • PyPI organizations accepted Qt!
    • We heard about https://wheelnext.dev/ it seems some ideas could be beneficial.
  • Infra & Releases
    • A few issues in our CI in the last weeks (fixed now)
    • Qt 6.8.3 new snapshot coming
    • Qt 6.9.0 (internal rc2 to test)
    • We will move 'dev' to use Python 3.10+
  • Bugs & Features
    • Windows on ARM wheels are ready after a couple of issues (linking) were fixed.
    • PYSIDE-3049 - Missing plugin for qmllint (fixed)
    • QML Bridges: Working on properties.
    • PYSIDE-3052 - QMessageLogger missing class (in progress)
    • Working on merging the contributions on QtRemoteObjects
    • PYSIDE-2854 - Support for [colocated objects|https://codereview.qt-project.org/c/pyside/pyside-setup/+/632241] in shiboken (structs issue, might support c++ unions)
    • PYSIDE-3040 GTK Theming issue with PySide install
    • Qt 6.10 adaption continues
    • Speed of overriding methods (previously cached) - new fix is improving the performance, but duck-punching was not properly working.
      • Can this be excluded from the caching?
    • The list of new improvements for type hints keeps growing (which is good!) so many issues has been solved.
    • We might need to find a solution for the implicit conversions we do (like qdatetime/py_datetime)
    • Discussion about Optional and pointer arguments that have a default value.
    • Some property types (public class variables) are missing type information

13. March 2025

  • General
  • Infra & Releases
    • Windows on ARM research continues and looks good! managed to fix an issue, but a new issues was found on samplebinding. The issue might be related to missing OpenGL.
    • 6.9.0rc might be released tomorrow, which means PySide6 FF will be due.
  • Bugs & Features

6. March 2025

  • General
    • Jaime's internal presentation will be next Monday at 11am
    • QtCS registration is up.
    • Discussion on IPC options for Qt developers.
  • Infra & Releases
    • 6.9 Qt for Python FF happening next week.
    • Windows on ARM deployment test failing.
  • Bugs & Features
    • Remote object contributions are going well, and we might merge them for 6.9
    • Binary size reduction research continued, but it seems we have reached the reduction we can, without touching the C++ side of our bindings.
    • PYSIDE-3012 Type hints issues were addressed (typing.Sequence -> typing.Collection) even if it is a simple change in theory, to change it internally and for our generation it took a lot of time.
      • Removing object-inheritance in the pyi files
      • White-space around equal operators issue (default parameters)
    • Update Widget Gallery example
    • Changed to adapt std::chrono patches in shiboken (identify overloads and choose the better option)
    • Cleaning up some bug reports, metamethod connection issue fixed.
    • Addressing some coverity issues for Designer
    • Started 6.10 adaption.
    • QML Next works continues.
    • Changes in the build system scripts are still in progress, some stuff is broken when used, but it's going in a good direction.
    • Finalizing the pyside6-project changes to adapt the pyproject.toml changes.
    • Addressing new found QtCreator issues with the pyproject.toml compatibility.

27. February 2025

  • General
    • Windows on ARM improving
  • Bugs & Features
    • PYSIDE-2701 Size reduction, investigating removing redundant overloads
    • PYSIDE-2701 Size reduction, trying wrapper folding, needs massive reordering
    • PYSIDE-3012 replacement of typing.Sequence by collections.abc.Sequence
      • Identified incompatibility with Python < 3.9.8 and Python < 3.10.1, fixed by small patch
      • First change finally done, needs series of further changes
    • 6.10 adaption continues
    • PYSIDE 2942 Slot type annotation fix
    • QTBUG-132266 Checked the code on macOS that the user uploaded, no issues were found related to PySide or macOS.

20. February 2025

  • General
    • QtWS possible participation
    • QtCS has a priority of bringing more external contributors
  • Infra & Releases
    • 6.9 RC February 28th (maybe postponed)
    • Windows on ARM test cases failing due to mypy fast cache (requires rust toolchain, that's currently missing from the CI). static libclang doesn't work on ARM builds (but does in x86_64).
    • RTA trials continue, possibility to use qtpip
  • Bugs & Features
    • PYSIDE-2701 Size reduction for virtual functions patch was merged
    • PYSIDE-3002 painted virtual functions solved (even though we had our own opinion about performance)
    • 3020 SignalInstance disconnect issue fixed
    • Templates/snippets cleanup in the typesystem.
    • 6.10 adaption continues
    • QtCreator toml changes:
      • psyide6-project adaption to the latest changed related
    • QtDS changes postponed (to be available in QtDS 4.8)
    • PYSIDE-3017 QSerialBus overload order issue was fixed
    • PYSIDE-3012 Still addressing issues (CI currently failing)
    • qtqa improving the wheel testing process.
    • Brainstorming a better approach for QML Next
    • Finishing the folding patches, they don't make a lot of sense at the moment due to previous changes (being added into shiboken)


13. February 2025

  • General
    • Did you know Shiboken translates into "Death Sword"? 死某剣
    • QtCS happening after QtWS in Munich in early May.
    • Qt Design Studio integration (internal presentation) with Python to be prepared.
  • Infra & Releases
    • Windows on ARM research continues.
    • QtDS wheels to be updated for the new release
    • 6.9.0 RC by the end of the February.
    • RTA testing initiative to be restart
    • Evaluating scikit-core-build for replacing build_scripts/
  • Bugs & Features
    • Flatpak issue was solved (cleanup)
    • Brainstorming ideas for QML Next (preparing internal presentation)
    • Android wheel names to be adapted https://packaging.python.org/en/latest/specifications/platform-compatibility-tags/#android
    • Qt Creator finishing .toml support for Python Projects.
    • Qt DS Python changes ready to be merged
      • Tutorial changes to be prepared
    • Type hints heuristic evaluation in order to address newly found issues related to overloads with similar shape.
    • Handling of value-types in shiboken (refactoring, new features and doc)
    • PYSIDE-3005 OpenGL issues were fixed
    • PYSIDE-3013 Font issue was fixed
    • PYSIDE-3015 OpcUA support bug fixed
    • PYSIDE-3014 virtual function on QSpinBox issue fixed
    • 6.9 adaption patches
      • Found newly moc changes were breaking our enums
    • Size Reduction
      • hashing functions to re-use them.
      • changing the policy to use absolute size measure (sizebench)
      • Removing a few things from the folding patch, in order to merge it
    • PYSIDE-2997 and PYSIDE-3003 type hints issues were solved. A couple are still open.

6. February 2025

  • General
    • We went to FOSDEM and meet many PySide users!
    • Commercial / LTS naming on the Installer.
  • Infra & Releases
    • Reviewing our branching policies. There is interest in branching pyside-setup sooner.
    • We might need to move the Android wheels to PyPI (Probably from 6.9 on)
    • 6.8.2.1 release is planned in order to fix the missing DLLs in Windows (MSVC)
      • cheery pick is missing for 5.15
    • PySide6_DS 4.7 to be released in the next couple of weeks.
  • Bugs & Features
    • Adding TOML support for Python projects in QtCreator
    • TypeHints new reports, trying to get an idea of what's causing the errors
    • Issues in Flatpak: updating version, checking a cleanup issue. Addressing dependencies issues for optional packages.
    • QtQA internal scripting: Adapting an automatic wheel download.
    • Size reduction
      • Move virtual function overrides. Only generated on the base classes.
      • Discovered and fixed a few multiple inheritance with shiboken
    • Snippets translation tool: Trying to add a feature to use fully qualified enums.
    • clang-tidy warnings were fixes
    • Handling value types on non-default constructors (inspired by 6.9 changes)
    • Discussion on moving away out internal building process to scikit-build
    • Size reduction (folding approach): To publish first results soon.
    • Supporting team member with pyi session to understand the internal mechanism.
    • Ideas from the size reduction research were implemented
    • Changing the benchmark code for the size reduction (which might not include the new changes to shiboken)

30. January 2025

  • General
  • Infra & Releases
    • Preparing 6.8.2
  • Bugs & Features
    • Size reduction PYSIDE-2701 : Implemented code reuse for Python overrides of virtual functions
    • QtPythonScripting: continue working on multiple inheritance, added more widgets
    • Size reduction: PYSIDE-2701 Folding progress: We can now combine multiple foldings of the same function. This will bring some more reduction.
    • Simplebrowser example updated
    • adding imageviewer docs

23. January 2025

  • General
  • Infra & Releases
    • Windows on ARM configuration testing.
    • 6.8.2 scheduled release next week, and branching will happen today.
  • Bugs & Features
    • QtPythonScripting: continue working on Stable ABI support and multiple inheritance
    • [ext] 6.9 Designer release issues with macOS drag and drop + bug fixing
    • PYSIDE-2990 Slot Executed in Signal's Thread Even With Auto & QueuedConnection
      • People is getting the documentation from an outdated wiki page, which is causing new reports.
      • Wiki will be updated.
    • Size reduction: we generate a lot of code for parsing keyword arguments. The code was moved to libshiboken and the size was reduced 3%
      • Optimization reviews: it seems it's only the virtual functions, but not the actual bindings.
    • Size reduction: Windows is giving some issues for special characters, which seems to be also present in Linux.
    • Cross compiling and creating wheels with the new JNI classes bindings. Trying to test them in an emulator, found other issues.
    • pyside6-deploy/project and DS changes integrating, hopefully they will be merged today \o/
    • DS-only changes are still in review.
    • TOML integration - continue research on adding new format for python projects
    • QtGraphWidgets issue with yocto build was fixed.

16. January 2025

  • General
    • Highly probable that one of us will go to FOSDEM to help with the Qt Project stand! so if you /reader/ are going, drop by and say hi!
  • Infra & Releases
    • 6.8.2 will be released on 23th January so far, so we expect providing the wheels in the following days.
    • 3.13 on the CI still on-going.
    • 6.5.4 OSS released
  • Bugs & Features
    • Discussion about QJni* bindings when cross compiling.
      • It did built (and installed) for aarch64 and x86_64 but armv7a will be tried later on.
      • The main issue with this story was that it was bindings only for cross compiled pyside
    • Exploring toml compatibilities within QtCreator
    • DS patches still needs review.
    • Binary size work continues
      • 17% reduction so far, and this could be included in the future-features list.
      • Once is ready, we might provide an option to disable it to go back to the more readable wrapper code.
      • We might evaluate a template approach once the solution is out, to avoid maintaining regexes.
    • Remote Object reviews ready in order to merge changes (only a few details)
    • Qt Python Scripting
      • Multiple inheritance is not supported yet.
      • REPL function to help development
      • Research on Limited API usage.
      • find_python macro in 3.26 allow to find the stable abi
    • docstring changes in order to expose them as docstring per methods.
      • some experiment to add it to the pyi files, but it doesn't show.

09. January 2025

  • General
    • FOSDEM 2025: Qt got a stand!
    • Internal Hackathon going on.
  • Infra & Releases
    • https://download.qt.io/official_releases/QtForPython/ got restructured and it's now very tidy
    • Preparing 6.8.2
    • 6.8.1.1 Windows and Linux wheels were uploaded for consistency thanks to user-reports when uploading only the 6.8.1.1 on macOS due to a missing module
    • Tests with 3.13 on the CI
  • Bugs & Features
    • PYSIDE-2966 Disabled instantiating non-instantiable classes
    • PYSIDE-1735 Examples and tests were ported to use fully qualified enumerations
    • Python Scripting continues (enable adding __repr__ functions)
    • Discussion about QJni* bindings when cross compiling.
      • We might try a few new configurations for adding this bindings.
    • Tutorial for Boot2Qt and PySide apps deployment
    • Doc changes: adding comments for using uv
    • QML Next: still working on improved decorators for a smoother integration
    • Qt Remote Objects: Big set of patches by external contributor
    • Binary size reduction work continues with new ideas from other projects: folding, string handling, renaming, etc.
    • Yocto builds issues with LLVM still not solved.

2024

2023

2022

2021

2020

2019

2018

Retrieved from "https://wiki.qt.io/index.php?title=Qt_for_Python_Development_Notes&oldid=44070"