From ece.cinucen at qt.io Fri Oct 9 09:59:10 2026 From: ece.cinucen at qt.io (=?iso-8859-1?Q?Ece_Cin=FC=E7en?=) Date: Fri, 9 Oct 2026 07:59:10 +0000 Subject: [PySide] Qt for Python release: 6.12.0 is out! Message-ID: Dear Community, we are happy to announce that 6.12.0 is available. You can read the full changelog here: https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.12.0 Here is the blogpost: https://www.qt.io/blog/qt-for-python-release-6.12-is-here A few highlights of the release: - The new QtQmlFeatures module (Technical Preview) provides reactive properties for QML. Decorators such as @auto_properties, @computed, @watch and @effect reduce the boilerplate needed to expose Python values to QML. - iOS support has been added. PySide6 applications can be deployed to iOS devices and the simulator with the new pyside6-ios-deploy tool. - Security has been hardened, based on a threat analysis done for the EU Cyber Resilience Act. Issues such as zip slip, shell injection and unsafe deserialization have been fixed. - pyside6-deploy can now be configured in pyproject.toml and builds standalone packages by default. - Android deployment now supports Python 3.10 to 3.14 and devices with 16 KB memory pages. - QtWebEngine and QtPdf are now shipped as separate wheels. - Initial support for Python 3.15. - General bug fixing on PySide and Shiboken. As always, give us a hand by reporting bugs, asking for new examples, tutorials, videos, etc on JIRA https://wiki.qt.io/Qt_for_Python/Reporting_Bugs and drop by our platforms to get in touch in: https://wiki.qt.io/Qt_for_Python#Community We hope you enjoy 6.12! Have a nice weekend! Best Regards, -- Ece Cin?cen Specialist Software Engineer The Qt Company GmbH Erich-Thilo-Str. 10 12489 Berlin, Germany ece.cinucen at qt.io +49 157 85319426 www.qt.io Gesch?ftsf?hrer: Mika P?lsi, Juha Varelius, Juha Puputti Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B [https://www.qt.io/] [https://www.facebook.com/qt/] [https://twitter.com/qtproject] [https://www.linkedin.com/company/qtgroup/] [https://www.youtube.com/QtStudios] Confidential -------------- next part -------------- An HTML attachment was scrubbed... URL: From leonelmosqueda12 at gmail.com Fri Oct 9 22:41:41 2026 From: leonelmosqueda12 at gmail.com (Leo Mosqueda) Date: Fri, 9 Oct 2026 13:41:41 -0700 Subject: [PySide] Build/source records for PySide6 6.11.0 macOS universal2 wheels Message-ID: Hello Qt for Python team, Could you point me to the producer build records for these published 6.11.0 wheels? - pyside6-6.11.0-cp310-abi3-macosx_13_0_universal2.whl SHA-256: 1f2735dc4f2bd4ec452ae50502c8a22128bba0aced35358a2bbc58384b820c6f - pyside6_essentials-6.11.0-cp310-abi3-macosx_13_0_universal2.whl SHA-256: 85d6ca87ef35fa6565d385ede72ae48420dd3f63113929d10fc800f6b0360e01 - pyside6_addons-6.11.0-cp310-abi3-macosx_13_0_universal2.whl SHA-256: d5eaa4643302e3a0fa94c5766234bee4073d7d5ab9c2b7fd222692a176faf182 - shiboken6-6.11.0-cp310-abi3-macosx_13_0_universal2.whl SHA-256: d88e8a1eb705f2b9ad21db08a61ae1dc0c773e5cd86a069de0754c4cf1f9b43b The public wheel hashes, 6.11.0 source-archive metadata and general build documentation are available. I have not identified the record connecting these exact wheel artifacts to their effective build inputs. Could you provide links to: 1. A release/build receipt, attestation or specific Coin/Gerrit build record connecting these wheel hashes to the Qt, PySide and Shiboken source revisions, including any patches. 2. The effective Qt build configuration and embedded/system component selections, or a build-specific SBOM, particularly the FreeType and HarfBuzz versions used in the arm64 slice. 3. The corresponding source/build materials and any documented relinking or library-replacement instructions applicable to these wheels. Existing records would be sufficient. If another official channel handles these requests, please point me there. Thank you. From admin.zaiclox5 at gmail.com Sun Oct 18 08:02:19 2026 From: admin.zaiclox5 at gmail.com (Muhamad Rozaimi) Date: Sun, 18 Oct 2026 14:02:19 +0800 Subject: [PySide] Build provenance for official PySide6 6.9.2 Windows x64 wheels Message-ID: Hello Qt for Python team, RZM Network is reviewing the open-source release materials for ZaiMiXplorer, a Windows application branded ZaiCloX5. We use the official PySide6_Essentials, PySide6_Addons, and shiboken6 6.9.2 cp39-abi3-win_amd64 wheels. We have the published Qt and PySide source archives, but need to identify the build inputs and third-party source corresponding to the binaries in those wheels. Could you point us to a release-specific build record or SPDX SBOM, or answer the following? 1. What Qt/PySide/Shiboken source revisions, configuration options, build patches, and third-party dependency versions produced the published Windows wheels? If a build-specific SBOM exists, where is it available? 2. The wheel?s qjpeg.dll identifies libjpeg-turbo 3.0.3, whereas the Qt 6.9.2 source declaration identifies 3.1.1. Which libjpeg-turbo source and patches correspond to this binary, and is it statically linked? 3. Which PDFium revision, build options, and nested third-party components produced Qt6Pdf.dll, Qt6PdfWidgets.dll, and qpdf.dll? Where are the notices applicable to those wheel binaries? 4. Which Mesa and LLVM sources, patches, and build settings produced the bundled opengl32sw.dll? Its binary indicators point to Mesa 11.2.2 and LLVM 3.6.2, but we have not established the exact build provenance. 5. Are there release-specific materials or instructions for replacing LGPL-covered Qt/PySide/Shiboken components from these wheels when redistributed in a PyInstaller onedir application? For unambiguous identification, the PyPI wheel SHA-256 values we reviewed are: - PySide6_Essentials: b2f746f795138ac63eb173f9850a6db293461a1b6ce22cf6dafac7d194a38951 - PySide6_Addons: 98d2413904ee4b2b754b077af7875fa6ec08468c01a6628a2c9c3d2cece4874f - shiboken6: 68c33d565cd4732be762d19ff67dfc53763256bac413d392aa8598b524980bc4 Thank you for any build records, source links, or a pointer to the appropriate team. RZM Network ZaiCloX5 admin.zaiclox5 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dc at dcsoft.com Thu Oct 22 19:02:52 2026 From: dc at dcsoft.com (David Ching) Date: Thu, 22 Oct 2026 10:02:52 -0700 Subject: [PySide] Build provenance for official PySide6 6.9.2 Windows In-Reply-To: References: Message-ID: <043201dd6247$2ce13660$86a3a320$@dcsoft.com> I'm also distributing a proprietary application, using the official PySide6/Qt binaries, currently version 6.10.2, under LGPLv3. It hadn't occurred to me that we had to list Qt's embedded dependencies as you are attempting to do. I believe I am fulfilling the open source obligations. See https://dcsoft.com/Products/TimeStitcherAcknowledgements. Included on this page: Third-Party Components Included in Qt TimeStitcher redistributes official PySide6, Shiboken6, and Qt binaries. These binaries may incorporate additional open-source components maintained by third parties. The Qt Project maintains the corresponding third-party license attributions and software bill of materials. See: Third-Party Code Used in Qt -- https://doc.qt.io/qt-6.10/licenses-used-in-qt.html Qt Software Bill of Materials -- https://doc.qt.io/qt-6.10/licenses-used-in-qt.html I presume these references are sufficient but would be welcome to hear of corrections. Thanks, David -----Original Message----- Date: Sun, 18 Oct 2026 14:02:19 +0800 From: Muhamad Rozaimi To: pyside at qt-project.org Subject: [PySide] Build provenance for official PySide6 6.9.2 Windows x64 wheels Message-ID: Content-Type: text/plain; charset="utf-8" Hello Qt for Python team, RZM Network is reviewing the open-source release materials for ZaiMiXplorer, a Windows application branded ZaiCloX5. We use the official PySide6_Essentials, PySide6_Addons, and shiboken6 6.9.2 cp39-abi3-win_amd64 wheels. We have the published Qt and PySide source archives, but need to identify the build inputs and third-party source corresponding to the binaries in those wheels. Could you point us to a release-specific build record or SPDX SBOM, or answer the following? 1. What Qt/PySide/Shiboken source revisions, configuration options, build patches, and third-party dependency versions produced the published Windows wheels? If a build-specific SBOM exists, where is it available? 2. The wheel?s qjpeg.dll identifies libjpeg-turbo 3.0.3, whereas the Qt 6.9.2 source declaration identifies 3.1.1. Which libjpeg-turbo source and patches correspond to this binary, and is it statically linked? 3. Which PDFium revision, build options, and nested third-party components produced Qt6Pdf.dll, Qt6PdfWidgets.dll, and qpdf.dll? Where are the notices applicable to those wheel binaries? 4. Which Mesa and LLVM sources, patches, and build settings produced the bundled opengl32sw.dll? Its binary indicators point to Mesa 11.2.2 and LLVM 3.6.2, but we have not established the exact build provenance. 5. Are there release-specific materials or instructions for replacing LGPL-covered Qt/PySide/Shiboken components from these wheels when redistributed in a PyInstaller onedir application? For unambiguous identification, the PyPI wheel SHA-256 values we reviewed are: - PySide6_Essentials: b2f746f795138ac63eb173f9850a6db293461a1b6ce22cf6dafac7d194a38951 - PySide6_Addons: 98d2413904ee4b2b754b077af7875fa6ec08468c01a6628a2c9c3d2cece4874f - shiboken6: 68c33d565cd4732be762d19ff67dfc53763256bac413d392aa8598b524980bc4 Thank you for any build records, source links, or a pointer to the appropriate team. RZM Network ZaiCloX5 admin.zaiclox5 at gmail.com From xristos_velocity at yahoo.com Fri Oct 23 17:11:28 2026 From: xristos_velocity at yahoo.com (xristos_velocity at yahoo.com) Date: Fri, 23 Oct 2026 15:11:28 +0000 (UTC) Subject: [PySide] Source and build details for PySide6 6.11.2 Windows wheels Message-ID: <22214474.18933.1792768291827@yahoo.com> Hello, We are preparing a Windows desktop application for sale and want to provide the correct source for the Qt libraries included with it. We use PySide6 6.11.2 Windows x64 packages, bundled with PyInstaller. The included Qt libraries report version 6.11.2. Could you point us to: 1. The source revisions used for these Windows packages. 2. Any patches applied to Qt or its Python bindings, or confirmation that there were none. 3. The build instructions and settings needed to rebuild the included libraries. The package includes Core, Gui, Widgets, Network, OpenGL, Svg, Qml, QmlMeta, QmlModels, QmlWorkerScript and Quick. It also includes platform, style, image, touch, network-information and security plugins. We have the released qtbase, qtdeclarative, qtsvg, qtimageformats and pyside-setup 6.11.2 source archives. We want to check whether anything else is needed before providing them to customers. Thank you. From juradoalvarezedgarpaul at gmail.com Sat Oct 24 02:05:23 2026 From: juradoalvarezedgarpaul at gmail.com (EP JA) Date: Fri, 23 Oct 2026 19:05:23 -0500 Subject: [PySide] Source/build provenance and build-specific SBOM for PySide6 6.11.1 Windows wheels Message-ID: Hello Qt for Python team, I am resending this inquiry after confirming my mailing-list subscription; the initial attempt was rejected as a non-member post. We are preparing a proprietary Windows desktop application using the PySide6, PySide6_Essentials, PySide6_Addons and shiboken6 6.11.1 cp310-abi3 win_amd64 wheels obtained through PyPI. We are assessing the applicable open-source licensing route, not requesting legal certification or claiming a commercial license. The attached technical ZIP contains artifact-identities.json, which lists the four exact wheel names and SHA-256 values, 76 shipped files that match wheel members and RECORD, retained source-archive identities, FFmpeg exported configurations and Chromium version declarations. It does not contain our proprietary source, binaries or user data. We found Qt's SBOM documentation but no files with recognizable SBOM/SPDX/ CycloneDX/build-provenance names in these four retained wheels. Could you point us to existing published material for these exact builds, or clarify its availability? 1. Corresponding source commits, patches, build recipes/configuration and toolchain information for the Qt, PySide and Shiboken binaries in these wheels. 2. A build-specific SBOM or equivalent third-party manifest for WebEngine, Chromium and Qt PDF. If hashes differ from another Qt distribution, how should that manifest be related to the wheel binaries? We do not assume that an installer SDK's SBOM automatically describes the PyPI wheels. 3. The Chromium revision/patch selection and relevant multimedia build flags. The retained source declares chrome/VERSION 140.0.7339.225 while its CHROMIUM_VERSION describes base 140.0.7339.264 with security patches up to 148.0.7778.96. We would like to understand that relationship for these wheels. 4. Build provenance and changes for the five external FFmpeg DLLs, including the actual zlib source/version used. The exported configuration mentions zlib-1.3.1 paths; we do not treat that path as proof of the linked version. 5. Existing instructions for building compatible modified replacements, including required matching bindings/plugins. Generic build instructions help, but do not by themselves identify the original wheel build. Our local checks establish artifact identity and partial configuration correspondence, not a complete source/build or third-party licensing closure. If another public project channel is more appropriate, please direct us there. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: MORPHY_consulta_tecnica_Qt_NO_ENVIADA.zip Type: application/x-zip-compressed Size: 8529 bytes Desc: not available URL: