[PySide] Qt for Python release: 6.7.1 is out!

[Cristián Maureira-Fredes via PySide]

Hello everyone,

we are happy to tell you that 6.7.1 is now available

As usual, you can get it with a:

pip install pyside6

or update your current installation via

pip install pyside6 -U

This release addresses many issues that were found
in 6.7.0, so we encourage you to give it a try.

- Some bugs regarding the newly introduced Lazy load
was fixed, which was affecting polymorphic Qt classes,
- A NoneType issue, a syntax error, and missing imports in our .pyi 
files were fixed,

- Many newly discovered missing classes were exposed to Python,
- and a couple of crashes for qmlRegisterType and QtQml.ListProperty
were fixed.

If you want to read more changes, check them out here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.7.1

In case you find an issue, let's know!
https://bugreports.qt.io/projects/PYSIDE

Keep an eye on our platforms, and join any of them
https://wiki.qt.io/Qt_for_Python#Community

Have a nice weekend!

Cheers
--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] New Qt for Python release: 6.7.0 is here!

[Cristián Maureira-Fredes via PySide]

On 4/12/24 9:51 AM, Cristián Maureira-Fredes via PySide wrote:



On 4/11/24 2:26 PM, Antonio Rojas wrote:
El jueves, 11 de abril de 2024 14:18:45 (CEST), Shyamnath Premnadh 
escribió:


 > Hi,

 >

 > You can find the sources here - 
https://code.qt.io/cgit/pyside/pyside-setup.git/?h=6.7.0


 >

 > Regards,

 > Shyamnath  


Thanks, but why is there no git tag? Getting the sources from the a 
branch head is highly non-standard. And is Qt no longer planning to 
provide taballs for PySide?


It's not a decision of not having a tag, but more like the tag was
forgotten, and we will trying to get the issues related the sources 
first in place.


I'm certain the tag will be up soon,
also the sources are already on:
https://download.qt.io/official_releases/QtForPython/pyside6/PySide6-6.7.0-src/
because the issues related to the upload were fixed.

Cheers




quick update:
the v6.7.0 was pushed :)

Cheers

--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] New Qt for Python release: 6.7.0 is here!

[Cristián Maureira-Fredes via PySide]

On 4/11/24 2:26 PM, Antonio Rojas wrote:

El jueves, 11 de abril de 2024 14:18:45 (CEST), Shyamnath Premnadh escribió:

 > Hi,

 >

 > You can find the sources here - 
https://code.qt.io/cgit/pyside/pyside-setup.git/?h=6.7.0


 >

 > Regards,

 > Shyamnath  


Thanks, but why is there no git tag? Getting the sources from the a 
branch head is highly non-standard. And is Qt no longer planning to 
provide taballs for PySide?


It's not a decision of not having a tag, but more like the tag was
forgotten, and we will trying to get the issues related the sources 
first in place.


I'm certain the tag will be up soon,
also the sources are already on:
https://download.qt.io/official_releases/QtForPython/pyside6/PySide6-6.7.0-src/
because the issues related to the upload were fixed.

Cheers



--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] New Qt for Python release: 6.7.0 is here!

[Cristián Maureira-Fredes via PySide]

On 4/11/24 2:12 PM, Antonio Rojas wrote:

Hello,

  Where can we find the sources? The 
https://download.qt.io/official_releases/QtForPython/pyside6/PySide6-6.7.0-src/  dir is empty and there is no 6.7.0 tag on the git repo.





Hey Antonio,

There was an issue with the release of the source,
and we are currently trying to address the problem, so hopefully
the sources are soon up, and it was relating with the missing
tag, in the meantime, if you need this soon,
you can rely on the 6.7.0 branch:

https://code.qt.io/cgit/pyside/pyside-setup.git/log/?h=6.7.0

Sorry for the inconvenience.

Cheers

--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] New Qt for Python release: 6.7.0 is here!

[Cristián Maureira-Fredes via PySide]

Dear community,

we are happy to announce that 6.7.0 is finally available.
It took us some extra time for some last minute issues,
but they were solved.

https://www.qt.io/blog/qt-for-python-release-6.7

The full change log can be found in:

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.7.0

If you want a summary:
- Improvements to the QtAsyncio.
- We use lazy imports now, getting from 35-40% improvement when 
importing Qt modules.

- Improvements to the Android deployment.
- Better tools documentation and new examples.
- Thanks to QtCreator's team, there is now Python kits.
- Python 3.8 support was dropped
- On going work on the dynamic bindings, QtDS compatibility, Yocto 
images, and macOS permission API.


As always, give us a hand by reporting bugs, asking for new examples, 
tutorials, videos, etc on JIRA https://bugreports.qt.io/projects/PYSIDE


and drop by our community platforms in
https://wiki.qt.io/Qt_for_Python#Community

We hope you enjoy 6.7!

Have a nice week!

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] problem with __init__ and QObject

[Cristián Maureira-Fredes via PySide]

Hello Trevor,

For that specific case, I'd recommend you
call the A constructor first:

from PySide6.QtCore import QObject

class A:
def __init__(self, val=1):
print(f"A {val}")


class B(A, QObject):
def __init__(self):
A.__init__(self, val=2)
QObject.__init__(self)

bb=B()



which prints
A 2



Cheers

On 18/03/2024 20:31, Clarke, Trevor wrote:

*
Ball Aerospace is now part of BAE Systems, Inc. with a new sector name – 
Space & Mission Systems. Learn more here. 
<https://www.baesystems.com/en-us/our-company/inc-businesses/space-and-mission-systems>*


from PySide6.QtCore import QObject

class A:

     def __init__(self, val=1):

     print(f"A {val}")

class B(QObject, A):

     def __init__(self):

     QObject.__init__(self)

     A.__init__(self, val=2)

bb=B()

output is

A 1

A 2

How do I correctly call the A init only once with args?

**

*Trevor Clarke***

/Senior Software Engineer/

Space & Mission Systems Sector, BAW Systems, Inc.

T: +1-937-416-7167 | E: trevor.cla...@ballaerospace.com

Fairborn, OH | Pronouns: He/Him

baesystems.com


___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.6.2 is out!

[Cristián Maureira-Fredes via PySide]

Hello everyone,

we are happy to tell you that 6.6.2 is now available

As usual, you can get it with a:

pip install pyside6

or update your current installation via

pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.6.2

In case you find an issue, let's know!
https://bugreports.qt.io/projects/PYSIDE

Keep an eye in our platforms, and join any of them
https://wiki.qt.io/Qt_for_Python#Community

Have a nice weekend!

Cheers

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] adding pyside6 to yocto build

[Cristián Maureira-Fredes via PySide]

On 1/26/24 15:53, Belisko Marek wrote:

Hi,

Just want to ask as I'm new in pyside etc. I have an qt app which was 
written using python. I want to run my app on an embedded device so I 
would need to add pyside dependency. For my board I'm using Yocto to 
build the final image. I checked Pyside is available on pypi.org 
but arm64 is built for python 3.8 while Yocto has 3.10. Would that work or do I need to somehow compile pyside and other tools using Yocto?


Thanks.

marek




Hey Marek,

The wheels on PyPi are 'cp38-abi3'
that means that they are compatible with all the officially release
Python versions starting from 3.8, that means that
3.9, 3.10, 3.11, and 3.12 are supported as well.
In case you are interested into this topic, here
is the documentation: https://docs.python.org/3/c-api/stable.html

Regarding yocto, that's something we are currently
investigating in order to include PySide in the Qt images
provided by the Qt Installer (Maintenance Tool), but
it's still not available.

In case you find any further issue,
let us know, but using those wheels should be enough.

Cheers

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.6.1 is out!

[Cristián Maureira-Fredes via PySide]

Hello everyone,

we are happy to tell you that 6.6.1 is now available

As usual, you can get it with a:

pip install pyside6

or update your current installation via

pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.6.1

In case you find an issue, let's know!
https://bugreports.qt.io/projects/PYSIDE

Keep an eye in our platforms, and join any of them
https://wiki.qt.io/Qt_for_Python#Community

Have a nice weekend!

Cheers

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Python templates in Qt Creator

[Cristián Maureira-Fredes via PySide]

Hey,


there was some discussion time ago that more templates could be added to 
Qt Creator. The development team is interested to know which templates 
do you think might be a good idea to include.


This is the bug report issue: 
https://bugreports.qt.io/browse/PYSIDE-2372 in case you want to comment, 
or you could do it here.


[ There is an image on the forum post with the same topic in case
you want to see the current ones: 
https://forum.qt.io/topic/152532/python-templates-in-qt-creator ]


For example, I recently pushed a new one to see if it would make sense 
one project that uses QML_ELEMENT to expose a Python class to QML. 
https://codereview.qt-project.org/c/qt-creator/qt-creator/+/498769


Any thoughts?

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] qtpip 0.1 released!

[Cristián Maureira-Fredes via PySide]

Hey there,

For our Qt License holders out there,
we just released qtpip.

qtpip is a simple wrapper around pip,
that adds some logic from the Qt Installer
in order to provide a quick way to get
commercial Qt for Python wheels.

The current approach to get commercial wheels
was very tedious and more complicated that just using pip,
so we believe this is the right mechanism
to simplify that use case.


In order to use it, one needs to install it via:

pip install qtpip

and then use it like you will do with pip:

qtpip install pyside6

That will check if you currently have a valid Qt License
and will enable you to get commercial wheels in your
environment.

Here you can find more info!
https://www.qt.io/blog/qtpip-qtforpython-installer

And in case you have ideas,
or find an issue, use the 'Qt pip'
component in the Qt Bug Tracker:
https://bugreports.qt.io/issues/?jql=project%20%3D%20PYSIDE%20AND%20component%20%3D%20%22Qt%20pip%22

Cheers!

--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] New Qt for Python release: 6.6.0 is here!

[Cristián Maureira-Fredes via PySide]

Dear community,

we are happy to announce that 6.6.0 is finally available.
It took us some extra time for some last minute regressions,
that luckily are solved.

https://www.qt.io/blog/qt-for-python-6.6

The full change log can be found in:

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.6.0

If you want a summary:
- QtGraphs was added to the project
- Python 3.7 support was dropped
- Python 3.12 support was added
- Shiboken Generator is now on PyPI
- Improved asyncio compatibility
- Improvements and examples for Android
- aarch64 wheels are now available
- Commercial wheels can be found soon on the Maintenance Tool
- Started research on dynamic bindings.

As always, give us a hand by reporting bugs, asking for new examples, 
tutorials, videos, etc on JIRA https://bugreports.qt.io/projects/PYSIDE


and drop by our community platforms in
https://wiki.qt.io/Qt_for_Python#Community

We hope you enjoy 6.6!

Have a nice week!

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.5.3 is out!

[Cristián Maureira-Fredes via PySide]

Hello,

After a couple of delays,
we are happy to tell you that 6.5.3 is now available

As usual, you can get it with a:

pip install pyside6

or update your current installation via

pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.5.3


In case you find an issue, let's know!
https://bugreports.qt.io/projects/PYSIDE

Keep an eye in our platforms, and join any of them
https://wiki.qt.io/Qt_for_Python#Community

Have a nice weekend!

Cheers
--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] PySide6 typing stubs available

[Cristián Maureira-Fredes via PySide]

Hey,

If you could provide that list
on a bug report it would be amazing,
otherwise messages here or in any chat platform
might be lost.

Cheers

On 8/6/23 17:44, Philippe Fremy wrote:

Hi Cristian,

The previous email was for pyside2 . I did a few bug reports but the 
feedback was that pyside2 is frozen, there will be no fixes.


For pyside6, I'll do some bug report eventually. For now, I want first 
to stabilize the project and get a big more traction into python static 
typing.


My jira login is bluebird75 in case you need to remember.

If you want in the meantime, I can list the general class of typing 
errors made by Qt.


Regards,

Philippe

Le 31/07/2023 à 09:55, Cristián Maureira-Fredes via PySide a écrit :

Hello Philippe,

I remember your previous email about the same project,
maybe I don't know your JIRA username, but
have you report all the incomplete or incorrect stubs
you mention?

As stated before, writing down the stubs it's not a problem,
but the challenge is to generate them automatically.

I personally don't believe maintaining stubs by hand
is something that scale over time, but I understand if this
is your personal project, and something you like.

Please report the issues if you haven't,
otherwise the problem you are trying to fix will never
be solved.

Cheers


On 7/30/23 00:18, Philippe Fremy wrote:

Hi,

Static typing python program is a growing trend with many benefits : 
better bug detection and better reliability for example.


Unfortunately, the stubs provided by default the pyside6 package are 
both incorrect and incomplete. But there is hope...


I have just released the pyside6-stubs package which provides 
noticeable improvements over the default stubs. For example :


  * add all missing signals to the stubs (many were missing)
  * fix QFileDialog.getOpen*() methods to accept None as parent argument
  * support all QSize and QSizeF operations
  * fix QTreeWidgetItem comparison with <
  * fix qVersion() returns string, not bytes
  * fix qDebug(), qWarning(), qCritical(), qFatal(), SIGNAL(), SLOT() to
    accept string, not bytes

And many more...

To benefit from this, install the pip package : 
https://pypi.org/project/PySide6-stubs/


To help improve the stubs or report any bug, it's here : 
https://github.com/python-qt-tools/PySide6-stubs


Regards,

Philippe


___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside




___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] PySide6 typing stubs available

[Cristián Maureira-Fredes via PySide]

Hello Philippe,

I remember your previous email about the same project,
maybe I don't know your JIRA username, but
have you report all the incomplete or incorrect stubs
you mention?

As stated before, writing down the stubs it's not a problem,
but the challenge is to generate them automatically.

I personally don't believe maintaining stubs by hand
is something that scale over time, but I understand if this
is your personal project, and something you like.

Please report the issues if you haven't,
otherwise the problem you are trying to fix will never
be solved.

Cheers


On 7/30/23 00:18, Philippe Fremy wrote:

Hi,

Static typing python program is a growing trend with many benefits : 
better bug detection and better reliability for example.


Unfortunately, the stubs provided by default the pyside6 package are 
both incorrect and incomplete. But there is hope...


I have just released the pyside6-stubs package which provides noticeable 
improvements over the default stubs. For example :


  * add all missing signals to the stubs (many were missing)
  * fix QFileDialog.getOpen*() methods to accept None as parent argument
  * support all QSize and QSizeF operations
  * fix QTreeWidgetItem comparison with <
  * fix qVersion() returns string, not bytes
  * fix qDebug(), qWarning(), qCritical(), qFatal(), SIGNAL(), SLOT() to
accept string, not bytes

And many more...

To benefit from this, install the pip package : 
https://pypi.org/project/PySide6-stubs/


To help improve the stubs or report any bug, it's here : 
https://github.com/python-qt-tools/PySide6-stubs


Regards,

Philippe


___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.5.2 is out!

[Cristián Maureira-Fredes via PySide]

Hello,

After a couple of delays,
we are happy to tell you that 6.5.2 is now available

As usual, you can get it with a:

pip install pyside6

or update your current installation via

pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.5.2


In case you find an issue, let's know!
https://bugreports.qt.io/projects/PYSIDE

Keep an eye in our platforms, and join any of them
https://wiki.qt.io/Qt_for_Python#Community

Have a nice weekend!

Cheers

--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Qt for Python release: 6.5.1 is out!

[Cristián Maureira-Fredes via PySide]

Hello,

we just released 6.5.1.1 to revert a fix
to a memory leak that was causing many issues
with some signals/slots that were registered
and executed wrongly.

The only change that this include is a revert of that fix.
You can find more details in the patch
https://codereview.qt-project.org/c/pyside/pyside-setup/+/481498
or visit the main issue:
http://bugreports.qt.io/browse/PYSIDE-2299
and some of the issues that were reported
https://bugreports.qt.io/browse/PYSIDE-2346
(with all the duplicated lists)

Sorry for the inconvenience
is that affected your project.

As always,
let's know of any other issue you encounter:
https://bugreports.qt.io/projects/PYSIDE

Cheers!

On 5/26/23 13:47, Cristián Maureira-Fredes via PySide wrote:

Hello everyone,

we are happy to tell you that 6.5.1 is now available

As usual, you can get it with a:

     pip install pyside6

or update your current installation via

     pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.5.1

In case you find an issue, let's know!
https://bugreports.qt.io/projects/PYSIDE

Keep an eye in our platforms, and join any of them
https://wiki.qt.io/Qt_for_Python#Community

Have a nice weekend!

Cheers



--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] redirect pyside.org to https://doc.qt.io/qtforpython-6/

[Cristián Maureira-Fredes via PySide]

Hey,


pyside.org redirects to https://wiki.qt.io/Qt_for_Python here
and that is what I asked the last time
the domain went unused some years ago.

If you have a different redirect in your machine,
I'd encourage you to use a private browsing tab
or report the bug directly to
https://bugreports.qt.io/projects/QTWEBSITE

Cheers

On 6/2/23 16:10, Florian Bruhin wrote:

Hey,


The reason to point pyside.org
is because due to the nature of the Qt project,
the wiki page is the closer we have to the Open Governance.
As you can see no other Qt project have their own domain,
that's why we decided to use it for the Wiki.

All three sites have references to each other.


pyside.org currently only seems to redirect to
a Microsoft Outlook sign-in page hosted on
outlook.office365.com.

Florian


___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] redirect pyside.org to https://doc.qt.io/qtforpython-6/

[Cristián Maureira-Fredes via PySide]

Hey Zhao Lee,

they have different purposes.

The main page is:
https://www.qt.io/qt-for-python

The main documentation page is:
https://doc.qt.io/qtforpython

and The main wiki is:
https://wiki.qt.io/Qt_for_Python

The reason to point pyside.org
is because due to the nature of the Qt project,
the wiki page is the closer we have to the Open Governance.
As you can see no other Qt project have their own domain,
that's why we decided to use it for the Wiki.

All three sites have references to each other.

Cheers

On 6/2/23 09:15, Zhao Lee wrote:
I'd suggest setting the domain pyside.org redirect to 
https://doc.qt.io/qtforpython-6/ <https://doc.qt.io/qtforpython-6/> 
<https://doc.qt.io/qtforpython-6/>



___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.5.1 is out!

[Cristián Maureira-Fredes via PySide]

Hello everyone,

we are happy to tell you that 6.5.1 is now available

As usual, you can get it with a:

pip install pyside6

or update your current installation via

pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.5.1

In case you find an issue, let's know!
https://bugreports.qt.io/projects/PYSIDE

Keep an eye in our platforms, and join any of them
https://wiki.qt.io/Qt_for_Python#Community

Have a nice weekend!

Cheers

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Pyside6: Support for JPEG2000 (Linux)

[Cristián Maureira-Fredes via PySide]

Hey Christian,

I couldn't find the plugin file on my install,
what's the full name of the plugin?
(I did have image formats on it but only found qjpeg
and libqjpeg)

Usually plugins needs just to be copied on the build directory
so they can be included in the package,
for example:

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/build_scripts/wheel_files.py?h=6.4#n417

where you can see it's just the plugin directory name is added
to the plugins list and then it will be included.
In 6.5.x we have a smarter mechanism, and we rely on the
modules information from a Qt build and get all the plugins
associated to the module:

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/build_scripts/wheel_files.py?h=6.5#n433

so it should be added automatically, as long as the Qt module
where it belongs is built.

For 6.4 I think you'd need to have your own PySide build,
but for 6.5.1+ it should be included. It would be better to open a 
ticket on JIRA so we don't forget but I'd try to remember

for this week :)

Cheers!



On 4/29/23 04:18, Christian Gagneraud wrote:

Hi there,

I'm using PySide 6.4 on Linux and I need to process JP2 images.
Qt has a plugin for JP2 on linux, it's called qjp2.
But this plugin is not available in PySide.

What is the best way to add support for this image format?
Can I build the plugin separately? Or do I need to build a full pyside
(and Qt) from scratch?
Neither way is satisfactory as this would require that I distribute
this custom pip package.

Any thoughts or advice?

Thanks,
Chris


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] New Qt for Python release: 6.5.0 is out!

[Cristián Maureira-Fredes via PySide]

Dear community,

we are happy to announce that 6.5.0 is available.

There are many cool things that we wrote in more detail
on the blog post, check it out!

https://www.qt.io/blog/qt-for-python-6.5

The full changelog can be found in:

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.5.0

If you want a summary:
- QtTextToSpeech, QtSerialBus, and QtLocation are now available
  (+ some extra API from other modules)
- Lots of issues related to the __feature__ option and
  multiple-inheritance are now fixed.
- Shiboken has support for std::array and std::span (experimental),
  plus a some options like to generate forward declarations instead
  of includes in the headers of each module.
- There is a really cool Qt Quick example now! the Filesystem Explorer.
- We are finishing up a tool to install commercial wheels easily
- Out asynchronous examples were polished, and more work is coming
  in the next releases.
- We have now initial support for Android deployment
- We looked into the NoGIL branch and pre-releases of Python 3.12
  to catch up with the future of Python

As always, give us a hand by reporting bugs, asking for new examples, 
tutorials, videos, etc on JIRA https://bugreports.qt.io/projects/PYSIDE


and drop by our community platforms in
https://wiki.qt.io/Qt_for_Python#Community

We hope you enjoy 6.5!

Have a nice week!


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Submitting App to Mac Store

[Cristián Maureira-Fredes via PySide]

Hey Pedro,

Glad you managed to reduce the amount of invalid symbols.

There is no other PySide distribution, so I think the safe bet
would be to build Qt, but only the modules you need by yourself
with that option, then building PySide only for those modules,
and then packaging your app, or wait for 6.5 which should not include 
those symbols according to 
https://codereview.qt-project.org/c/qt/qtbase/+/437376



Maybe you can try the RC wheels of PySide?
they can always be found in
https://download.qt.io/snapshots/ci/pyside/dev/latest/split_wheels/

and if those don't present the issue, maybe you just need to wait for
the official release of 6.5.0

If that doesn't work, it'd be something we'd need to explore for maybe
6.5.1 if possible.

Cheers!

On 3/31/23 09:42, Pedro Ferreira wrote:
Hello again, I've been able to get rid of the izma issues by building on 
a arm mac, that somehow improved things but they still complain about 
these 2:


Symbols: _responsibility_get_pid_responsible_for_pid, 
_responsibility_spawnattrs_setdisclaim


I found this ticket: https://bugreports.qt.io/browse/QTBUG-109032 
<https://bugreports.qt.io/browse/QTBUG-109032>
and apparently there's an option when building Qt that you can use: 
*-appstore-compliant*

*
*
Is there a build of PySide/Qt that was build with this option that I can 
use?

Thanks

On Tue, Mar 28, 2023 at 3:13 PM Pedro Ferreira <mailto:plferrei...@gmail.com>> wrote:


Hello Cristián, thanks for the reply. So are these symbols from
python rather than Qt?
I'll ask in another forum, thanks!

    On Mon, Mar 27, 2023 at 3:56 PM Cristián Maureira-Fredes via PySide
mailto:pyside@qt-project.org>> wrote:

Hey Pedro,

thanks for reaching out on this.

There are a couple of symbols that are guarded by the dev build
of Qt
https://codereview.qt-project.org/c/qt/qtbase/+/437376
<https://codereview.qt-project.org/c/qt/qtbase/+/437376>

But many of the others, like
_lzma_stream_encoder, _lzma_alone_decoder, etc
are present in CPython while building


https://github.com/python/cpython/blob/a059395921e4402c13a860aaa8fc44fea2023aa3/PCbuild/liblzma.vcxproj
 
<https://github.com/python/cpython/blob/a059395921e4402c13a860aaa8fc44fea2023aa3/PCbuild/liblzma.vcxproj>


It could be that also there are some artifacts from pyinstaller,
but I don't have experience getting applications to the App Store
so you might want to ask on the forum.qt.io <http://forum.qt.io>
or in some apple related
forum. Maybe there people with more experience might help you.

Cheers


On 3/27/23 10:42, Pedro Ferreira wrote:
 > Hello, I have an application written with PySide that I'm
trying to
 > submit to the Mac Store. I'm using PyInstaller to package it
and sign it.
 >
 > I submitted the app but on the review process I got a
rejection with
 > this message:
 >
 >
 >     Your app uses or references the following non-public or
deprecated APIs:
 >     Symbols: _lzma_alone_decoder, _lzma_get_check, _lzma_end,
 >     _lzma_stream_decoder, _lzma_properties_size,
 >     _lzma_check_is_supported, _lzma_raw_decoder,
 >     _lzma_properties_encode, _lzma_auto_decoder, _lzma_code,
 >     _lzma_properties_decode, _lzma_easy_encoder,
_lzma_lzma_preset,
 >     _lzma_stream_encoder, _lzma_alone_encoder, _lzma_raw_encoder,
 >     _responsibility_spawnattrs_setdisclaim,
 >     _responsibility_get_pid_responsible_for_pid
 >
 >
 >
 > The use of non-public or deprecated APIs is not permitted on
the App
 > Store, as they can lead to a poor user experience should
these APIs
 > change and are otherwise not supported on Apple platforms.
 >
 >
 >
 > I'm assuming this comes from Qt/PySide but have no idea how I
can solve
 > this. Is there a different build that I can use that maybe
doesn't have
 > these symbols? Or some other idea, not sure what to do.
 >
 > Thanks
 >
 > ___
 > PySide mailing list
     > PySide@qt-project.org <mailto:PySide@qt-project.org>
 > https://lists.qt-project.org/listinfo/pyside
<https://lists.qt-project.org/listinfo/pyside>

-- 
Dr. Cristián Maureira-Fredes

Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lin

Re: [PySide] Submitting App to Mac Store

[Cristián Maureira-Fredes via PySide]

Hey Pedro,

thanks for reaching out on this.

There are a couple of symbols that are guarded by the dev build of Qt
https://codereview.qt-project.org/c/qt/qtbase/+/437376

But many of the others, like
_lzma_stream_encoder, _lzma_alone_decoder, etc
are present in CPython while building

https://github.com/python/cpython/blob/a059395921e4402c13a860aaa8fc44fea2023aa3/PCbuild/liblzma.vcxproj


It could be that also there are some artifacts from pyinstaller,
but I don't have experience getting applications to the App Store
so you might want to ask on the forum.qt.io or in some apple related
forum. Maybe there people with more experience might help you.

Cheers


On 3/27/23 10:42, Pedro Ferreira wrote:
Hello, I have an application written with PySide that I'm trying to 
submit to the Mac Store. I'm using PyInstaller to package it and sign it.


I submitted the app but on the review process I got a rejection with 
this message:



Your app uses or references the following non-public or deprecated APIs:
Symbols: _lzma_alone_decoder, _lzma_get_check, _lzma_end,
_lzma_stream_decoder, _lzma_properties_size,
_lzma_check_is_supported, _lzma_raw_decoder,
_lzma_properties_encode, _lzma_auto_decoder, _lzma_code,
_lzma_properties_decode, _lzma_easy_encoder, _lzma_lzma_preset,
_lzma_stream_encoder, _lzma_alone_encoder, _lzma_raw_encoder,
_responsibility_spawnattrs_setdisclaim,
_responsibility_get_pid_responsible_for_pid



The use of non-public or deprecated APIs is not permitted on the App 
Store, as they can lead to a poor user experience should these APIs 
change and are otherwise not supported on Apple platforms.




I'm assuming this comes from Qt/PySide but have no idea how I can solve 
this. Is there a different build that I can use that maybe doesn't have 
these symbols? Or some other idea, not sure what to do.


Thanks

___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.4.3 is out!

[Cristián Maureira-Fredes via PySide]

Hello everyone,

we are happy to tell you that 6.4.3 is now available

As usual, you can get it with a:

pip install pyside6

or update your current installation via

pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.4.3

In case you find an issue, let's know!
https://bugreports.qt.io/projects/PYSIDE

Keep an eye in our platforms, and join any of them
https://wiki.qt.io/Qt_for_Python#Community

Have a nice rest of the week!

Cheers
--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] LGPL licensing obligations

[Cristián Maureira-Fredes via PySide]

Hey David,

On 1/13/23 18:20, David Ching wrote:

For now, I just posted a written offer.  The app is not expected to have 
widespread interest, I would be surprised if anyone bothered to ask.  If they 
do, I will get the needed info at the time.  I would be interested in 
commercially licensing Qt under the startup plan (it is $500/year), but it is 
vague whether this is an option any more, and when it was, they claimed to 
audit tax documents to check the revenue is less than a certain amount, and I 
don’t have a separate entity set up for that.


For that is better to contact a salesperson directly
https://www.qt.io/contact-us



Meanwhile, I could not find the source to the pyside6 wheel... does anyone know 
if this is available?  If so, I could redistribute that.  Or maybe I can just 
zip up what is installed with “pip install PySide6” and call it a day.


That information lives in the public wiki page: https://pyside.org
and the official documentation: https://doc.qt.io/qtforpython (in the 
Install and build from source)


The repository is https://code.qt.io/cgit/pyside/pyside-setup.git/



The Qt for Python licenses for what it uses are at 
https://doc.qt.io/qtforpython/licenses.html but I don’t use any of the affected 
functionality, so I don’t think I have to include them.  I haven't found the 
webpage listing the C++ Qt licenses of what it uses yet.


PySide most of the Qt modules, in case you include a module that has a 
special license, you'll need to include it. For example, if you use 
QtWidgets, at the end of each page like:

https://doc.qt.io/qt-6/qtwidgets-index.html#licenses
you find the used licenses.


Does anyone know of any existing PySide6 LGPL projects where these deployment 
issues have been resolved?  The process of LGPL licensing of Qt for Python 
might itself by open sourced!  😊


Not that I'm aware of.



Thanks,
David



Cheers!

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.4.2 is out!

[Cristián Maureira-Fredes via PySide]

Hello everyone,
and happy new year!

We hope you have a nice 2022, and
wish you a better 2023 full of Qt and Python :)

As usual, you can get 6.4.2 with a:

pip install pyside6

or update your current installation via

pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.4.2

In case you find an issue, let's know!
https://bugreports.qt.io/projects/PYSIDE

Keep an eye in our platforms, and join any of them
https://wiki.qt.io/Qt_for_Python#Community

Have a nice rest of the week!

Cheers
--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] What happened to manylinux wheels for python3.8+?

[Cristián Maureira-Fredes via PySide]

Hey,

The old 'manylinux1' where never really manylinux1,
there was an internal hack in order to make them 'look like manylinux1'.
The reason of that, is due to the incompatibility of
any manylinux* tag, with the minimum Qt requirements.

Starting from 6.3.0 we adopted a new PEP to distribute
our Linux wheels, PEP600 [1] which allowed us to describe
the glibc version the package was using, instead of
the old approach.

Another thing we noticed, is that when we use
the stable ABI, and rely on the abi3 tag,
you only need to specify the minimum Python version,
meaning this:

cp36.cp37.cp38.cp39.cp310-abi3

could be written like this:

cp36-abi3

Furthermore,
in the past, we had users that for some reason
needed to build PySide using a different Qt version.
This was rare, so we decided to also drop the tags
that were describing both version PySide.Qt in:

PySide6-6.2.4-6.2.4

using only the pyside version

PySide6-6.2.4


On top of that,
we reached a point that the PySide6 wheel was too large,
because it was including all the modules.
Many people argued, "why do I need webengine, multimedia, ..."
if I only want to have a simple PySide application?

So we split the wheels [2] [3].
Installing pyside6 for new users, will install
pyside6_essentials, and pyside6_addons wheels,
so in your case, you'd need to uninstall and then install pyside6
again, because pip cannot detect the change in wheel structure.

With that information, answering your questions:

1) if you are 'updating', then the solution is to uninstall and install
pyside6 again.
2) Installing pyside6, and not updating.

As long as you have glibc 2.28+ and a recent pip (run: pip install -U 
pip) you would be able to install, because the PEP600 was included

in pip 20.3 (2020-11-30).

If you have any more question, let us know!


[1] https://peps.python.org/pep-0600/
[2] https://www.qt.io/blog/qt-for-python-details-on-the-new-6.3-release
[3] 
https://doc.qt.io/qtforpython/gettingstarted/package_details.html#package-details


On 12/9/22 20:16, dynobo via PySide wrote:


Hi,

I've noticed for an application which I package as AppImage, that I 
can't install PySide versions more recent than 6.2.4.


When inspecting the distribution files on PyPi and 
https://download.qt.io/official_releases/QtForPython/pyside6/ it seems 
to me, that after 6.2.4 the builds changed:


Manylinux wheel files for 6.2.4 got build for various Python versions:
PySide6-6.2.4-6.2.4-cp36.cp37.cp38.cp39.cp310-abi3-manylinux1_x86_64.whl

After that, they only seem to be build for Python 3.7:
PySide6-6.4.1-cp37-abi3-manylinux_2_28_x86_64.whl

1.) Can this be the reason why I can't update beyond 6.2.4 inside my 
AppImage (I'm using Python 3.9)?


2.) Any ideas, how I could use the most recent PySide6 versions inside 
an AppImage again?


Any help or hints is appreciated! 😄
Thanks & best regards!
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.4.1 is out!

[Cristián Maureira-Fredes via PySide]

Hey there,

It took us some extra days this time,
but we are happy to inform you that 6.4.1 is out!
You can get it as:

pip install pyside6

or update your current installation via

pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.4.1

There were many bug fixes around signals, signatures,
tooling, build system, and refactoring, so give it a spin :)


This is the last release of the year,
so hopefully you will have some time to check this version
out and let us know of any issue so we can fix them
for 6.4.2.
https://bugreports.qt.io/projects/PYSIDE

Keep an eye in our platforms, and join any of them
https://wiki.qt.io/Qt_for_Python#Community

Have a nice rest of the week!

Cheers
--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] What if a slot is not decorated with @Slot()?

[Cristián Maureira-Fredes via PySide]

Hello,

The answer can be found in
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside6/libpyside/dynamicqmetaobject.cpp#n557

The main idea is to register Slots (and signals) at parsing time,
before the connection is done.

An old issue can be find here:
https://bugreports.qt.io/browse/PYSIDE-315
with some discussion as well.

I hope that helps,
Cheers

On 11/16/22 06:47, Zhao Lee wrote:
The doc says 
:


It is really important to decorate each method declaration with a
@Slot(), in that way PySide6 knows internally how to register them
into Qt.

But the method used as the slot works well even without the @Slot() 
decorator , I wonder if there is a risk in doing so.



___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] New Qt for Python release: 6.4.0.1 is out!​

[Cristián Maureira-Fredes via PySide]

Hey,

due to a couple of issues with 6.4.0,
we decided not to keep everyone waiting
until 6.4.1 and did a new release: 6.4.0.1

You can now install PySide6 using Python 3.11,
among other tiny fixes.

More details in case yo are interested are described in the blog post:
https://www.qt.io/blog/qt-for-python-6.4.0.1-release

and if you just want to see what else is there, check the changelog:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.4.0.1

Have a nice Thursday!

Cheers


--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Semantic Versioning

[Cristián Maureira-Fredes via PySide]

On 10/18/22 22:26, ic...@gmx.net wrote:

Hello,

I'd like to bring up a topic to discussion which I know the QT project 
takes very serious and I'd like to know if there are any plans to 
implement this also on PySide6 and shiboken6.


Semantic versioning seems to be a widely adopted standard in many 
projects (for details, see https://semver.org/). It basically means that 
a library maintains backward compatibility when changing the minor 
version number and it maintains forward/backward compatibility when 
changing the patch version number (this is usually used for bugfix 
releases).


In (C++) QT, the rules are even more strict, because QT guarantees also 
binary backward compatibility when increasing the minor version number. 
This basically means that it should be possible to use QT shared objects 
6.4.0 for a project originally compiled against 6.0.0 
(https://wiki.qt.io/Qt-Version-Compatibility).


In PySide / Qt for Python the version number seems not to give a lot of 
guarantees. For example, the enum change introduced in 6.4.0 (with the 
preview introduced in 6.3.1) doesn't seem to maintain backward 
compatibility (a project written for 6.0.0 doesn't work anymore with 
6.4.0). Admittetly, the "forgiveness mode" solves some (or most) of the 
issues, but the blog post does mention cases where this is not going to 
work. And I have found also a few cases which broke (see my previous 
message). Obviously, the environment variable approach with 
PYSIDE63_OPTION_PYTHON_ENUM is not maintaining backward compatibility 
either. Therefore, a project respecting semantic versioning rules would 
have needed to change the major version number for this change.


The situation gets even more unclear when shiboken comes into the game 
additionally. When you have a project which uses shiboken to generate 
python bindings for c++ classes (which additionally depend on C++ QT), 
even switching between patch numbers has been binary incompatible very 
often. I didn't try with 6.x.x versions, but I assume that this is still 
the case? This is a pity because this basically means that the PySide6 
dependency of such a project is a strict "PySide6==6.minor.patch" 
because PySide6 has a dependency to "shiboken6==6.minor.patch". I'd love 
to see at least binary compatibility between the patch versions, but 
this would require the shiboken API to be binary compatible, which was 
not the case in the 5.x.x versions.


So the question is: Are we going to see more backward compatibility in 
the future of PySide6 / shiboken6? Will there ever be any guarantees?


Kind Regards
Christoph


Hello,

thanks for your interest.

# The short answer:
The only compatibility we can provide in this situation
is within minor releases, we cannot include new features in major
releases only because then due to the slow development cycle in Qt,
we would be tied to old Python version for too long.

# The long answer:
We are in a very special position with the Qt for Python project,
where we are trying to find a middle ground of what does the Qt project
and C++ community needs/wants/uses, and what the Python community
needs/wants/uses.

Initially, the first limitation was to provide the module
for the many Python versions, including back then, support for Python 
2.7 and 3.x. We were tied to Python 2.7 for more than a year

after it was deprecated because we didn't want to drop support on
a minor version, which is sane, many people sadly were still on that
version, so we made the decision to drop Python 2 support in Qt 6
releases.
In the meantime, there were Python minor releases that were adding
new features that users wanted to use, but we couldn't because we
decided for a long time to adhere to the Python Limited API [1];
in case you are not familiar with it is just a set of functions
that are guaranteed to work from Python 3.6+, so the pro
is that we need only 1 Python package (wheel) for Python 3.X,
instead of one per-version. The cons is that we cannot use
new features/API internally.

With that information, let's jump into the Enum change.
Due to the compatibility between Python 2 and 3,
Shiboken implemented an ad-hoc Enum system to mimic Qt enums,
and bring them to Python, the main motivation was that
Python didn't have any Enum mechanism in the 2 version,
so we used that, and kept it around. But Python
introduced the enum module in 3.4, so we really wanted
to avoid re-implementing the wheel (no pun intended) and having
our own Enum scheme was not optimal, so the work to migrate
to the Python enum system, started.
Additional motivation here was that PyQt, the set of bindings
developed by Riverbank, was also heavily using the enum module
for Qt 6 related wheels - we wanted to ensure people could
move around PySide and PyQt without much trouble.
So we did the release of the feature in 6.3.1 so people could
be able to test, and have a smoother transition to 6.4,
which by many reasons depending of the reality of developers,
they are unable to do

Re: [PySide] New Qt for Python release: 6.4.0 is out!

[Cristián Maureira-Fredes via PySide]

Hello,

Can you try to install PySide6 on a fresh virtual environment
and verify this?

If you are unfamiliar with that:
https://doc.qt.io/qtforpython/quickstart.html


It might be that you are installing everything on your system Python,
and then there might be some issues with upgrades.

Cheers

On 10/17/22 02:05, David Ching wrote:



From: Cristi?n Maureira-Fredes  
Subject: [PySide] New Qt for Python release: 6.4.0 is out!


New tools: pyside6-qml (for qml preview), pyside6-qtpy2cpp (to translate

python to c++ code), pyside6-deploy (to simplify the deployment story, based
on nuitka)

pyside6-qtpy2cpp seems to be missing after PIP install on Windows.  The
other utilities including pyside6-deploy are present:

C:\Users\David\AppData\Roaming\Python\Python39\Scripts>dir /b pyside6* |
grep deploy
pyside6-deploy.exe

C:\Users\David\AppData\Roaming\Python\Python39\Scripts>dir /b pyside6* |
grep cpp

C:\Users\David\AppData\Roaming\Python\Python39\Scripts>




___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] where to download the complete QtPDF example ?

[Cristián Maureira-Fredes via PySide]

Hello Zhao Lee,

If you read the second paragraph in
https://doc.qt.io/qtforpython/examples/index.html
it says:

> You can find all these examples inside the pyside-setup on the
> examples directory, or you can access them after installing PySide6
> from pip inside the site-packages/PySide6/examples directory.

Meaning, that if you have your virtual environment in

/home/user/env

you can go inside

/home/user/env/lib/python3.10/site-packages/PySide6/examples/

and find all the examples from the project.

Another option is cloning the pyside-setup repository,
and jump into the pyside-setup/examples/ directory,
and a third option is to navigate the code.qt.io
and download the files one-by-one

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/examples/pdf/quickpdfviewer


I hope it helps,
Cheers


On 10/14/22 07:32, Zhao Lee wrote:

I found there is a QtPDF example at
https://doc.qt.io/qtforpython/examples/example_pdfwidgets__pdfviewer.html?highlight=qtpdf
 
<https://doc.qt.io/qtforpython/examples/example_pdfwidgets__pdfviewer.html?highlight=qtpdf>
I want to download and give it a try, but the images in resources.qrc 
are missing , where can I get the complete example ?


___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] New Qt for Python release: 6.4.0 is out!

[Cristián Maureira-Fredes via PySide]

Dear Community,

we are really happy to let you know that 6.4.0 is finally out.
It took us a bit more time due to many issues with the CI,
and unavailability of the team due to conferences and COVID,
but it's finally out :)

A blog post with all the details was just published here:
https://www.qt.io/blog/qt-for-python-release-6.4-is-finally-here
and you can view the full changelog here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.4.0

In case you want the summary, the highlights are:

- New modules: QtPdf, QtPdfWidgets, QHttpServer, and QtSpatialAudio

- New API: qHash, qt_set_sequence_auto_mnemonic(), 
glGet(Boolean|Double|Float|Integer)v(), 
glGet(Boolean|Double|Float|Integer)i_v(), 
QWebEngineCookieStore.setCookieFilter(), 
QtWebEngineProfile.setNotificationPresenter(), 
QQmlContext.setContextProperties(), QAudioBuffer.data() and 
QAudioBuffer.constData()


- No we support PyPy 3.9, and you can get the wheels via pip, because 
they are uploaded to PyPi.


- In case you have a local build of Python 3.11, this release is 
compatible with the last RC


- New examples: surface_numpy, minimalsurface, dropsite, dirview, 
googlesuggest, license wizard, heart rate server/client, qml 
window/plugins, analog clock, digital clock, spreadsheet, terminal, 
character map.


- The new Enum system is now the default behavior.

- New tools: pyside6-qml (for qml preview), pyside6-qtpy2cpp (to 
translate python to c++ code), pyside6-deploy (to simplify the 
deployment story, based on nuitka)


- and many more things!


As always, give us a hand by reporting bugs, asking for new examples, 
tutorials, videos, etc on JIRA https://bugreports.qt.io/projects/PYSIDE


and drop by our community platforms in
https://wiki.qt.io/Qt_for_Python#Community

We hope you enjoy 6.4!

Cheers

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.3.2 is out!

[Cristián Maureira-Fredes]

Dear Community,

maybe you noticed already, but if not
we wanted to tell you that 6.3.2 is out!

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.3.2

Besides many bug fixes,
you will find some improvements to the docs,
new examples, and changes to the
new Enum system that will be the default behavior
in 6.4, as soon as the docs are out we will
let you know again so you can be aware.

In case you haven't heard, we are changing
the Enum/Flags behavior in 6.4 (you can try
it now as well with the PYSIDE63_OPTION_PYTHON_ENUM=1
environment variable) to drop the historical
implementation, and start using real Python Enums
for all the Qt Enums.

If you are using PyPy,
the wheels can be found in:
https://download.qt.io/official_releases/QtForPython/pypy/


As always, if you find any problem, let us know
by reporting an issue
https://bugreports.qt.io/projects/PYSIDE

Remember to join any of the current community
platforms: https://wiki.qt.io/Qt_for_Python#Community

Have a nice weekend!
Cheers


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] signal connection only works with lambda

[Cristián Maureira-Fredes]

Hey Frank,

Could you maybe share more code using
services like pastebin.com or any other?

Images are a bit hard to understand, because
often they lack of context.

If you think you encounter a bug,
maybe you can open a bug report,
but for that, please share the code of a minimal reproducible
example [1]

Cheers

[1] https://wiki.qt.io/Qt_for_Python/Reporting_Bugs

On 9/1/22 06:00, Frank Rueter wrote:

Hi Christian,

sorry for the delay.
Yes, the signal is declared in the class but not inside any function.
I had not used the @Slot decorator but tried it just now to no avail.
image.png
image.png
image.png

On Tue, Aug 30, 2022 at 7:21 PM Cristián Maureira-Fredes 
mailto:cristian.maureira-fre...@qt.io>> 
wrote:




On 8/30/22 00:08, Frank Rueter wrote:
 > Hi all,
 >

Hey Frank,

 > probably a pre-coffee hiccup:
 > I have this weird issue where my signal connection only works when
 > utilising lambda, even though the data type sent by the signal is
 > exactly what the receiving slot needs.
 > This is my code:
 >
 > In a worker class (QRunnable) I emit this signal
 > *    tasks_data_available = QtCore.Signal(list)
 > *
 >

Just a sanity check:
That's declared inside a class, but not inside any method, right?

 > In my main widget I connect it like this:
 > *        worker.tasks_data_available.connect(self.__prep_task_data)
 > *
 > the slot looks like this:
 > *    def __prep_task_data(self, task_list):
 > *
 > *        print(task_list)*

Is this method decorated with a `@Slot(list)` ?

@Slot(list)
def __prep_task_data(elf, task_list):
      ...

 > I have done this countless times, but for some reason in this
case the
 > code never calls the slot when the QRunnable emits task_list.
 >
 > When I do this it works though:
 > *        worker.tasks_data_available.connect(lambda t:
 > self.__prep_task_data(t))
 > *

This might be due to the lazy registration of the lambda as a Slot,
without properly going through the Slot-registration process.

 > What am I missing? I should not have to use lambda in this case.

It might be the missing @Slot,
but let me know if that's not the case.

 > Cheers,
 > frank


Cheers

-- 
Dr. Cristián Maureira-Fredes

Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org <mailto:PySide@qt-project.org>
https://lists.qt-project.org/listinfo/pyside
<https://lists.qt-project.org/listinfo/pyside>



--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] examples/explainers for event filters?

[Cristián Maureira-Fredes]

On 8/31/22 18:17, Gordon L. Kindlmann wrote:




On Aug 31, 2022, at 2:36 AM, Cristián Maureira-Fredes 
 wrote:

You can check this example
that implements eventFilter
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/examples/network/googlesuggest
 (see googlesuggest.py)


Thanks for that suggestion; that's more useful than the other example I ran 
across:
https://forum.qt.io/topic/133106/installeventfilter-not-working-on-pyside6
which puts the event filter at the application level, rather than for a single 
widget.


But I have the feeling that this content represents some incomplete translation 
of C++ code ...


Yeah, indeed that's one of the wrongly translated snippets,
because the process is automated. Could you please open a bug report to fix it?


Sure, can you point out how to open such a bug report?
I didn't see any links on the documentation page in question.


Usually we put the community-focused content on the Public Wiki,
and we leave the documentation for tutorials, examples, and API comments.

When you go to pyside.org you will reach the public wiki,
where you can get:
https://wiki.qt.io/Qt_for_Python/Reporting_Bugs





Thanks,
Gordon


Cheers!

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] examples/explainers for event filters?

[Cristián Maureira-Fredes]

On 8/31/22 00:58, Gordon L. Kindlmann wrote:

Hello,


Hey!


I'm looking for simple examples or explainers on how to do event filtering in 
PySide6.  A google search result for:
pyside6 event filter examples
has as first result:
https://doc.qt.io/qtforpython/overviews/eventsandfilters.html#event-filters


You can check this example
that implements eventFilter
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/examples/network/googlesuggest 
(see googlesuggest.py)




But I have the feeling that this content represents some incomplete translation of C++ 
code and its description (the code has opening braces "{" and the text refers 
to true/false instead of True/False), so I'm not sure how much to trust this material.


Yeah, indeed that's one of the wrongly translated snippets,
because the process is automated. Could you please open a bug report to 
fix it?



I may be in the minority of PySide users in not having used Qt before, with 
only glancing interactions with C++, as I look to PySide as a better way to 
make guis for Python code.  These documentation glitches make me think I'm 
missing some other resources that are more specifically about PySide6.  Any 
advice?


You are not missing out other material,
personally, I always recommend people to check the 'examples'
for learning purposes.

The reason of having those mistranslated snippets
is because before, that was a manual process,
and due to the amount of snippets in Qt,
it was never even 20% done. So the team decided
to automatically translate the snippets,
which can provide more context, but with a price
of having some of them wrongly translated.
For that, we require feedback (like the one you gave!)
of which are the snippets that require a fix.


Thank you,
Gordon


Regarding that page,
you can find the C++ code as well:
https://doc.qt.io/qt-6/eventsandfilters.html

Once you file the bug report, we can do a manual
translation and provide the proper code snippets in
https://doc.qt.io/qtforpython/overviews/eventsandfilters.html#event-filters


Cheers!

--
Dr. Cristian Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Can't override paintEvent on QTableWidget

[Cristián Maureira-Fredes]

On 8/30/22 07:48, Frank Rueter wrote:

Hi all,


Hey there,

I am trying to override the paintEvent in a QTableWidget to draw a 
custom progressbar into the table area until the table data is loaded. I 
have done this with other widgets in the past but the table widget won't 
let me do this.

I am getting these errors:
QWidget::paintEngine: Should no longer be called
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter::setBrush: Painter not active

Here is a simple code snippet for testing:
https://gist.github.com/frueter/a5b722926a847c291d1472a6fd145dbf 
<https://gist.github.com/frueter/a5b722926a847c291d1472a6fd145dbf>


When I inherit from QWidget it works fine.
Is this sort of thing not possible with a QTableWidget?


It's because QTableWidget is a subclass of QTableView (and that's one 
from QAbstractScrollArea),

and AFAIK you need to open the painter based on the base viewport.

https://doc.qt.io/qt-6/qabstractscrollarea.html#paintEvent

and there you can see the hint to use the viewport.

In your code,
just replace:

painter = QtGui.QPainter(self)
by
painter = QtGui.QPainter(self.viewport())

and it should work. At least locally, I can see the gradient.


Cheers,
frank



Cheers

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] signal connection only works with lambda

[Cristián Maureira-Fredes]

On 8/30/22 00:08, Frank Rueter wrote:

Hi all,



Hey Frank,


probably a pre-coffee hiccup:
I have this weird issue where my signal connection only works when 
utilising lambda, even though the data type sent by the signal is 
exactly what the receiving slot needs.

This is my code:

In a worker class (QRunnable) I emit this signal
*    tasks_data_available = QtCore.Signal(list)
*



Just a sanity check:
That's declared inside a class, but not inside any method, right?


In my main widget I connect it like this:
*        worker.tasks_data_available.connect(self.__prep_task_data)
*
the slot looks like this:
*    def __prep_task_data(self, task_list):
*
*        print(task_list)*


Is this method decorated with a `@Slot(list)` ?

@Slot(list)
def __prep_task_data(elf, task_list):
...

I have done this countless times, but for some reason in this case the 
code never calls the slot when the QRunnable emits task_list.


When I do this it works though:
*        worker.tasks_data_available.connect(lambda t: 
self.__prep_task_data(t))

*


This might be due to the lazy registration of the lambda as a Slot,
without properly going through the Slot-registration process.


What am I missing? I should not have to use lambda in this case.


It might be the missing @Slot,
but let me know if that's not the case.


Cheers,
frank



Cheers

--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Packaging Qt for Python for *Linux

[Cristián Maureira-Fredes]

Hey there,

In case you are currently maintaining shiboken/pyside
for a *Linux OS, you might want to check a couple of issues
that were recently reported by the person currently
in charge of packaging Shiboken and PySide for Debian (thanks Lisandro!)

We have interacted in the past with folks maintaining the packages
for Fedora and Arch, but maybe someone else is on this list.

These issues contain some discussion on them:

https://bugreports.qt.io/browse/PYSIDE-2001 (signature_p.h, fixed)
https://bugreports.qt.io/browse/PYSIDE-2002 (shiboken path)
https://bugreports.qt.io/browse/PYSIDE-2003 (get_path scheme change)
https://bugreports.qt.io/browse/PYSIDE-2005 (soon to be merged)
https://bugreports.qt.io/browse/PYSIDE-2009 (cmake dir name change)
https://bugreports.qt.io/browse/PYSIDE-2010 (arch qualified so)
https://bugreports.qt.io/browse/PYSIDE-2020 (installation path)

Even if you have no problem with the suggested solution
or build process change, please let us know as well with a comment.

The changes might break your current packaging workflow,
so your opinion is crucial.

Thanks for your time!


--
Dr. Cristián Maureira-Fredes
Senior R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.3.1 is out!

[Cristián Maureira-Fredes]

Dear Community,

We are really happy to tell you that 6.3.1 is out!
It took us a couple of extra days but the wheels
were pushed to PyPi last Friday ;)

You can find the most important changes here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.3.1

This release contains fixes related compatibility issues
we had with older Python versions (3.7 and 3.9) due to the
fact that the wheels are generated with a higher version.

Some new API is around:
* like HBITMAP, HICON, and HRGN for Windows,
* QTest.qWait()/qSleep(),
* QAudioBuffer.data()/constData(),
* and if you use QLoggingCategory, qCDebug, qCInfo, qCWarning
  and qCCritical were added as well

Something really important that we encourage you to try,
is that we have in place an option, PYSIDE63_OPTION_PYTHON_ENUM
that you can define to change to the new Enum implementation.
We aim to get this in 6.4 as default behavior, so it's worth
the try before we jump into this feature.
The motivation behind this is to use Python Enums for all the
Qt Enums we have around, because until 6.3.0 we have been using
our own ad-hoc implementation.

On the Shiboken side of things,
you can now inject a function that retrieves the
type name of a polymorphic class,
the code related to type discovery is now generated
for all classes that contain an 'id expression' set,
among other things.

As always,
really crucial you can give us a hand by reporting
any strange or wrong behavior on the release
https://bugreports.qt.io/projects/PYSIDE

Remember to join any of the current community
platforms: https://wiki.qt.io/Qt_for_Python#Community

Have a nice week!
Cheers

--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Remove me

[Cristián Maureira-Fredes]

As a PSA
If you want to get out the mailing list,
you need to visit the url:

https://lists.qt-project.org/listinfo/pyside

and enter your information to do so.

Cheers


On 5/30/22 15:44, Simon Iványi wrote:


___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside





--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] QtConcurrent, run method alternative

[Cristián Maureira-Fredes]

On 5/25/22 15:58, Rute Mendes wrote:

Anyway, now I know why there're no examples for PySide, for future reference

https://stackoverflow.com/questions/32378719/qtconcurrent-in-pyside-pyqt 



Thanks.
Rute

A segunda, 23/05/2022, 13:20, Rute Mendes > escreveu:


Hi!

I've installed PySide6 but looking at docs there's no run method
implementation for QtConcurrent. What are the alternatives according
PySide availability, QtConcurrent, QFutureBaseInterface? ( and I
can't find examples only for PySide ).

Regards,

Rute


Hello Rute,

Due to the same reason you see there, that it's a namespace
we have been exploring how we could still expose at least a version
of the many overloads of functions like mappedReduced.

Another challenge, is that most of the QtConcurrent is heavily templated
what makes it a bit more tricky to expose to Python.

Out of curiosity,
have you tried to use Python-only options to achieve your goal?
not that I'm challenging the existence of QtConcurrent,
but I would like to understand the usage of the module over
some other options like:

threading, multiprocessing, concurrent.futures, etc
https://docs.python.org/3/library/concurrency.html

If having a Qt-API to handle concurrency is your motivation,
is a valid motivation IMHO :) or if QtConcurrent
is solving a problem that Python haven't solve yet
could be nice to know as well.

Cheers

--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Qt Designer is no longer shipped with the latest PySide6

[Cristián Maureira-Fredes]

Hello,

I just tested on Windows 10 (don't have 11), and designer is there.

Please to reproduce create a new environment
and install pyside6:

% python3.exe -m venv env
% env\Scripts\activate.bat
% pip install pyside6

(that will pyside6, pyside6-essentials, pyside6-addons, and shiboken6)
Then if you look inside 'env\Scripts'
you will have pyside6-designer.exe

If that still doesn't work for you,
please file a bug report https://wiki.qt.io/Qt_for_Python/Reporting_Bugs
with the content of your 'Scripts'
and 'PySide6/' directories (from your virtual environment).

Cheers

PS: In case you were not installing, but upgrading from PySide6 6.2.x
then please uninstall and install pyside6. Due to the changes
in the package structure, pip cannot resolve the new structure
and you end up with an empty installation.
https://www.qt.io/blog/qt-for-python-details-on-the-new-6.3-release


On 5/19/22 10:50, Zhao Lee wrote:

I tested with Python 3.9 on win11, there is no pyside6-designer







At 2022-05-19 00:20:28, "Cristián Maureira-Fredes" 
 wrote:

Hello,

it has never been removed:

% python -m venv env_test
% source env_test/bin/activate

% pip install pyside6
Collecting pyside6
  Using cached PySide6-6.3.0-cp36-abi3-manylinux_2_28_x86_64.whl (65 kB)
Collecting PySide6-Addons==6.3.0
  Using cached PySide6_Addons-6.3.0-cp36-abi3-manylinux_2_28_x86_64.whl 
(119.9 MB)

Collecting PySide6-Essentials==6.3.0
  Using cached 
PySide6_Essentials-6.3.0-cp36-abi3-manylinux_2_28_x86_64.whl (76.0 MB)

Collecting shiboken6==6.3.0
  Using cached shiboken6-6.3.0-cp36-abi3-manylinux_2_28_x86_64.whl (222 kB)
Installing collected packages: shiboken6, PySide6-Essentials, 
PySide6-Addons, pyside6
Successfully installed PySide6-Addons-6.3.0 PySide6-Essentials-6.3.0 
pyside6-6.3.0 shiboken6-6.3.0
WARNING: You are using pip version 22.0.4; however, version 22.1 is 
available.
You should consider upgrading via the 
'/home/cmaureir/env_test/bin/python -m pip install --upgrade pip' command.


% find env_test | grep pyside6-designer
env_test/bin/pyside6-designer


Cheers

On 5/18/22 13:23, Zhao Lee wrote:
I just found Qt Designer is no longer shipped with the latest PySide6, 
I'd suggest bringing it back for convenience





___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside





___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] PySide2 and PySide6 co-existing in same virtual environment

[Cristián Maureira-Fredes]

On 5/18/22 18:49, Nicholas Yue wrote:

Hi,

   I have a need to construct a Python virtual environment to install 
both PySide2 and PySide6 for migration purposes.


   Are the two modules PySide2 and PySide6 designed to be 
installed/co-exists and used in the same virtual environment.


   I did try it out on Windows10 Python 3.9.12 and installed both and 
was able to run

* pyside2-designer
* pyside6-designer

   Their about-box indicates they are pulling in their respective Qt 
5.15.2 and Qt 6.3.0


   Should I take the above as indicating all is well or are there other 
concerns I need to take into consideration?


Cheers
--
Nicholas Yue
https://www.linkedin.com/in/nicholasyue/ 
<https://www.linkedin.com/in/nicholasyue/>


Hey Nicholas!

Yes, both projects can coexist without any problem.
All the tools that wrap Qt tools ones like
designer, uic, rcc, etc have the prefix pyside2- or
pyside6- respectively.

The installation inside your site-packages/
will have directories PySide2/, PySide6/, shiboken2/ and shiboken6/
as well, where the Qt binaries will be located.

The only problem you might face is to rely
on the tools like uic, to generate a similar result.
pyside6-uic is way superior than pyside2-uic,
due to being the "real uic" instead of our own
Python-adaptation of that tool.

In case you encounter some problem,
let us know by reporting an issue 
https://wiki.qt.io/Qt_for_Python/Reporting_Bugs


Cheers


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Qt Designer is no longer shipped with the latest PySide6

[Cristián Maureira-Fredes]

Hello,

it has never been removed:

% python -m venv env_test
% source env_test/bin/activate

% pip install pyside6
Collecting pyside6
  Using cached PySide6-6.3.0-cp36-abi3-manylinux_2_28_x86_64.whl (65 kB)
Collecting PySide6-Addons==6.3.0
  Using cached PySide6_Addons-6.3.0-cp36-abi3-manylinux_2_28_x86_64.whl 
(119.9 MB)

Collecting PySide6-Essentials==6.3.0
  Using cached 
PySide6_Essentials-6.3.0-cp36-abi3-manylinux_2_28_x86_64.whl (76.0 MB)

Collecting shiboken6==6.3.0
  Using cached shiboken6-6.3.0-cp36-abi3-manylinux_2_28_x86_64.whl (222 kB)
Installing collected packages: shiboken6, PySide6-Essentials, 
PySide6-Addons, pyside6
Successfully installed PySide6-Addons-6.3.0 PySide6-Essentials-6.3.0 
pyside6-6.3.0 shiboken6-6.3.0
WARNING: You are using pip version 22.0.4; however, version 22.1 is 
available.
You should consider upgrading via the 
'/home/cmaureir/env_test/bin/python -m pip install --upgrade pip' command.


% find env_test | grep pyside6-designer
env_test/bin/pyside6-designer


Cheers

On 5/18/22 13:23, Zhao Lee wrote:
I just found Qt Designer is no longer shipped with the latest PySide6, 
I'd suggest bringing it back for convenience





___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] QtDesigner ???

[Cristián Maureira-Fredes]

On 4/25/22 21:20, David Ching wrote:

From: Paolo De Stefani 
Sent: Monday, April 25, 2022 11:27 AM
Subject: Re: QtDesigner ???


...

C:\Python310>pip install pyside6-essentials Collecting pyside6-essentials


Paolo, FWIW, I did a "pip install pyside6" and not the "pyside6-essentials".
Maybe that makes a difference.  Like I said, your code works fine here,
including with the "snake case" enabled.

Thanks,
David



Shouldn't be an issue, pyside6 installs pyside6-essentials
and pyside6-addons as dependencies.

Cheers


--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] QtDesigner ???

[Cristián Maureira-Fredes]

Hey,

it seems like your file got removed
due to a malware detection process.

Can you share your code using services like
pastebin.com dpaste.com linkode.org etc etc ?

In that case we can see the full extent of the problem.

As an alternative,
you can report a bug and share the zip file (or all the files)
to the issue, so it can be discussed there (you'd need a Qt account)
This is the platform to do that:
http://bugreports.qt.io/browse/PYSIDE
Make sure you select the 'pyside' project
and here you have more info:
https://wiki.qt.io/Qt_for_Python/Reporting_Bugs


Cheers

On 4/21/22 21:46, Paolo De Stefani wrote:

Il 20/04/2022 22:59 Cristián Maureira-Fredes ha scritto:

Hey,

(remember to reply to the list, so other folks can read the discussion,
I'm adding the ML on CC to jump back to the topic)


OPS... Sorry



Maybe you are hitting https://bugreports.qt.io/browse/PYSIDE-1561



It seems a diffrerent issue



Can you share more information regarding how you are using the generated
ui file?



It looks like a QtDesigner problem or uic problem for me BUT i'm not a 
professional programmer


I created a small script that can show the problem. Simply 
comment/uncomment line 33/34


#from Ui.DBManagerMainWindowGood import Ui_DBManagerMainWindow
from Ui.DBManagerMainWindowBad import Ui_DBManagerMainWindow

.ui files are included and you can see that the only difference between 
the 2 is a label and line edit added in the bad one. Of course both can 
be previewed in QtDesigner without any problem





--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] QtDesigner ???

[Cristián Maureira-Fredes]

Hey,

(remember to reply to the list, so other folks can read the discussion,
I'm adding the ML on CC to jump back to the topic)

Maybe you are hitting https://bugreports.qt.io/browse/PYSIDE-1561

Can you share more information regarding how you are using the generated
ui file?

You should be able to have 1 file with the option,
and another one without.

Let's say your generated file is this one:

---
from PySide6.QtWidgets import QLabel

class MyLabel(QLabel):
def __init__(self, parent=None):
super().__init__(parent)
# Using camelCase
self.setText("Hello")

def connectNotify(self):
pass
---

Which is not using snake_case,
then you can import it and use it:


---
import sys
from PySide6.QtWidgets import QApplication, QWidget, QHBoxLayout

from a import MyLabel

from __feature__ import snake_case

class MyWidget(QWidget):
def __init__(self, parent=None):
super().__init__(parent)

self.label = MyLabel()
# overriding the value, with snake_case
self.label.set_text("World")

layout = QHBoxLayout()
layout.add_widget(self.label)
self.set_layout(layout)

if __name__ == "__main__":

app = QApplication()
w = MyWidget()
w.show()
sys.exit(app.exec())
---

Executing that will have 'World' on the Widget.

When you use the __feature__ import shouldn't matter.

I hope it helps!

Cheers


On 4/20/22 17:30, Paolo De Stefani wrote:

Hi and thank for the quick response

The problem IS that the DBManagerMainWindow.py is generate by 
pyside6-uic not by me...

That's why i've attached the source .ui file and the resulting .py file

Do i need to remove from __feature__ import snake_case, true_property 
from my script for work correctly ???



Il 20/04/2022 14:09 Cristián Maureira-Fredes ha scritto:

Hello Paolo,

On 4/20/22 13:55, Paolo De Stefani wrote:

Hi
I've just upgraded to 6.3.0 and i'm hitting a weird problem
In a small program that i created years ago and that i've already 
ported to pyside6 some months ago with true property and snake case 
enabled i've decided to change a little bit the user interface
I did it in QtDisigner BUT now i don't understand why my application 
don't work


This is the error:

Traceback (most recent call last):
   File "c:\PyWare\pyDBManager\pyDBManager.py", line 1165, in 
 window = MainWindow()
   File "c:\PyWare\pyDBManager\pyDBManager.py", line 788, in __init__
 self.setupUi(self)
   File "c:\PyWare\pyDBManager\Ui\DBManagerMainWindow.py", line 208, 
in setupUi

 self.tab_widget_new_db.addTab(self.tab_create_db, "")
AttributeError: 'PySide6.QtWidgets.QGridLayout' object has no 
attribute 'isEmpty'



Is this related to the use of snake_case ?
DBManagerMainWindow.py is generated from DBManagerMainWindow.ui using 
c:\Python310\Scripts\pyside6-uic

QGridLayout HAS an IsEmpty attribute or maybe is_empty ???


Hello!

You can always try this without the whole application:


from PySide6.QtWidgets import QGridLayout
dir(QGridLayout)
[i for i in dir(QGridLayout) if 'empty' in i.lower()]

['isEmpty']

from __feature__ import snake_case
[i for i in dir(QGridLayout) if 'empty' in i.lower()]

['is_empty']


is you enable the 'snake_case' from __feature__
the method is called 'is_empty' instead of 'isEmpty'


Let's know if that did the trick!

Cheers


--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside




--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] QtDesigner ???

[Cristián Maureira-Fredes]

Hello Paolo,

On 4/20/22 13:55, Paolo De Stefani wrote:

Hi
I've just upgraded to 6.3.0 and i'm hitting a weird problem
In a small program that i created years ago and that i've already ported 
to pyside6 some months ago with true property and snake case enabled 
i've decided to change a little bit the user interface
I did it in QtDisigner BUT now i don't understand why my application 
don't work


This is the error:

Traceback (most recent call last):
   File "c:\PyWare\pyDBManager\pyDBManager.py", line 1165, in 
     window = MainWindow()
   File "c:\PyWare\pyDBManager\pyDBManager.py", line 788, in __init__
     self.setupUi(self)
   File "c:\PyWare\pyDBManager\Ui\DBManagerMainWindow.py", line 208, in 
setupUi

     self.tab_widget_new_db.addTab(self.tab_create_db, "")
AttributeError: 'PySide6.QtWidgets.QGridLayout' object has no attribute 
'isEmpty'



Is this related to the use of snake_case ?
DBManagerMainWindow.py is generated from DBManagerMainWindow.ui using 
c:\Python310\Scripts\pyside6-uic

QGridLayout HAS an IsEmpty attribute or maybe is_empty ???


Hello!

You can always try this without the whole application:

>>> from PySide6.QtWidgets import QGridLayout
>>> dir(QGridLayout)
>>> [i for i in dir(QGridLayout) if 'empty' in i.lower()]
['isEmpty']
>>> from __feature__ import snake_case
>>> [i for i in dir(QGridLayout) if 'empty' in i.lower()]
['is_empty']


is you enable the 'snake_case' from __feature__
the method is called 'is_empty' instead of 'isEmpty'


Let's know if that did the trick!

Cheers


--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] New Qt for Python release: 6.3.0 is out!

[Cristián Maureira-Fredes]

Hey there

The wheels are now published on PyPi,
you can drop the 'index-url' option and simply run:

pip install pyside6_essentials  # or
pip install pyside6

Cheers!


On 4/13/22 13:04, Cristián Maureira-Fredes wrote:

Dear Community,

we are really happy to let you know that 6.3.0 is finally out.
The whole team worked really hard on this release, due to all
the changes related to Qt/C++ 6.3, but also with new features
we are including.

A blog post with all the details was just published here:
https://www.qt.io/blog/qt-for-python-details-on-the-new-6.3-release

In case you are already reading this email,
let me summarize the release highlights :)

# Python compatibility

The 6.3.x series will be the last one supporting Python 3.6
because it reached the end-of-life. From 6.4.0 the minimum
required Python version will be 3.7

# Package Structure and Installation

Our wheels increased it size significantly after we included
the Apple Silicon compatibility, due to that, the same approach
would not escalate in our PyPi project, due to the hard 10G limit.

So we decided to split the wheels into Essentials, and Addons.
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/README.pyside6_essentials.md 

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/README.pyside6_addons.md 



This change might be incremental, but for you as end user it should
not affect you at all, neither if you are building from source.
Because a package called 'pyside6' remained, and that has a dependency
both Essentials and Addons wheels.

Sadly with this change, we didn't get the approval from the PyPi
team in time for the release, so the usual 'pip install'
requires an additional '--index-url' parameter to use Qt's servers
to get the latest version.


You can run:

     pip install pyside6 \

--index-url=https://download.qt.io/official_releases/QtForPython/split-wheels/ 



To get the 6.3.0 release. As soon as we get an approval, we will be
uploading the packages to PyPi.
We are sorry for this inconvenience.


The good aspect for this approach, is that you can use a reduced amount 
of modules only installing the 'pyside6_essentials' wheel:


     pip install pyside6_essentials \

--index-url=https://download.qt.io/official_releases/QtForPython/split-wheels/ 



Reducing the amount of extra large modules that maybe you application
was not using at all.



# Cross compilation

You can now cross compile Shiboken and PySide to a linux-based
embedded system.

A detailed tutorial can be found here:
https://doc.qt.io/qtforpython/gettingstarted.html#cross-compilation

This was released as a technical preview due to the limitations,
but we are looking forward to hear back from you.

Our development and testing was targeting Raspberry Pi 4 Model B,
in case your device is not supported, let us know to work on that!

# PyPy Compatibility

Well, this speaks on its own ;)
You can get the wheels from here:
https://download.qt.io/official_releases/QtForPython/pypy/

# pyside6-project

a new tool was added to automatically convert the .ui and .qrc
files, using the information from the .pyproject files.

Additionally, if you work with QML, the tool will search
for QML types and generate the .qmltypes file in case you want
to include qmllint into your workflow

# New look for the docs

After the change in the Qt documentation theme,
we needed to find a new look which provided a similar
experience.
You can check the new theme here:
https://doc.qt.io/qtforpython/

(Keep an eye for the upper-right icon to change between
light, dark and automatic themes)



As always, give us a hand by reporting bugs, asking for new examples, 
tutorials, videos, etc on JIRA https://bugreports.qt.io/projects/PYSIDE


and drop by our community platforms in
https://wiki.qt.io/Qt_for_Python#Community

We hope you enjoy 6.3!

Cheers



--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] New Qt for Python release: 6.3.0 is out!

[Cristián Maureira-Fredes]

Dear Community,

we are really happy to let you know that 6.3.0 is finally out.
The whole team worked really hard on this release, due to all
the changes related to Qt/C++ 6.3, but also with new features
we are including.

A blog post with all the details was just published here:
https://www.qt.io/blog/qt-for-python-details-on-the-new-6.3-release

In case you are already reading this email,
let me summarize the release highlights :)

# Python compatibility

The 6.3.x series will be the last one supporting Python 3.6
because it reached the end-of-life. From 6.4.0 the minimum
required Python version will be 3.7

# Package Structure and Installation

Our wheels increased it size significantly after we included
the Apple Silicon compatibility, due to that, the same approach
would not escalate in our PyPi project, due to the hard 10G limit.

So we decided to split the wheels into Essentials, and Addons.
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/README.pyside6_essentials.md
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/README.pyside6_addons.md

This change might be incremental, but for you as end user it should
not affect you at all, neither if you are building from source.
Because a package called 'pyside6' remained, and that has a dependency
both Essentials and Addons wheels.

Sadly with this change, we didn't get the approval from the PyPi
team in time for the release, so the usual 'pip install'
requires an additional '--index-url' parameter to use Qt's servers
to get the latest version.


You can run:

pip install pyside6 \

--index-url=https://download.qt.io/official_releases/QtForPython/split-wheels/

To get the 6.3.0 release. As soon as we get an approval, we will be
uploading the packages to PyPi.
We are sorry for this inconvenience.


The good aspect for this approach, is that you can use a reduced amount 
of modules only installing the 'pyside6_essentials' wheel:


pip install pyside6_essentials \

--index-url=https://download.qt.io/official_releases/QtForPython/split-wheels/

Reducing the amount of extra large modules that maybe you application
was not using at all.



# Cross compilation

You can now cross compile Shiboken and PySide to a linux-based
embedded system.

A detailed tutorial can be found here:
https://doc.qt.io/qtforpython/gettingstarted.html#cross-compilation

This was released as a technical preview due to the limitations,
but we are looking forward to hear back from you.

Our development and testing was targeting Raspberry Pi 4 Model B,
in case your device is not supported, let us know to work on that!

# PyPy Compatibility

Well, this speaks on its own ;)
You can get the wheels from here:
https://download.qt.io/official_releases/QtForPython/pypy/

# pyside6-project

a new tool was added to automatically convert the .ui and .qrc
files, using the information from the .pyproject files.

Additionally, if you work with QML, the tool will search
for QML types and generate the .qmltypes file in case you want
to include qmllint into your workflow

# New look for the docs

After the change in the Qt documentation theme,
we needed to find a new look which provided a similar
experience.
You can check the new theme here:
https://doc.qt.io/qtforpython/

(Keep an eye for the upper-right icon to change between
light, dark and automatic themes)



As always, give us a hand by reporting bugs, asking for new examples, 
tutorials, videos, etc on JIRA https://bugreports.qt.io/projects/PYSIDE


and drop by our community platforms in
https://wiki.qt.io/Qt_for_Python#Community

We hope you enjoy 6.3!

Cheers

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.2.4 is out!

[Cristián Maureira-Fredes]

Dear Community,

We are really happy to tell you that 6.2.4 is out!

You can find the most important changes here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.2.4

This release is focused mainly on a couple of high
priority issues we found with regards to snake_case,
signal and slots, and a few problems with some
methods.

As you might know, most of our efforts has been focused
on the soon-to-be-released 6.3, so we expect to have
a better PySide by that time, but for that we need your
help! check 6.2.4 out ;) play around with it, and let's
know if you find any problem!
https://bugreports.qt.io/projects/PYSIDE

Remember to join any of the current community
platforms: https://wiki.qt.io/Qt_for_Python#Community

Have a nice week!
Cheers


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.2.3 is out!

[Cristián Maureira-Fredes]

Hey folks,

It took us an extra couple of days this time,
but we are happy to inform you that 6.2.3 is out!
You can get it as:

pip install pyside6

or update your current installation via

pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.2.3

Remember to let us know if you find any issue with this release
by opening an issue on JIRA:
https://bugreports.qt.io/projects/PYSIDE

Drop by our platforms in case you are still suffering
by a bug we could prioritize before 6.3 is out

https://wiki.qt.io/Qt_for_Python#Community

or let us know any feedback regarding the documentation
https://doc.qt.io/qtforpython


Have a nice rest of the week!

Cheers
--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Qt for Python release: 6.2.2 is out!

[Cristián Maureira-Fredes]

Thanks for noticing!

the upload of the generator wheels was omitted,
but they will be uploaded now.

In case you discover something else, let's know :)


Cheers

On 12/16/21 11:01, ic...@gmx.net wrote:

Hi Cristián,

is there any chance to get an updated shiboken6_generator version as 
well? As it is now, I get dependency errors when trying to install the 
available shiboken6_generator 6.2.2 from 
https://download.qt.io/official_releases/QtForPython/shiboken6-generator/ together 
with the 6.2.2.1 PySide, that is because


  * PySide6 6.2.2.1 depends on shiboken6 6.2.2.1
  * shoboken6_generator depends on shiboken6 6.2.2

Kind Regards

Christoph

Am 12/9/21 um 12:43 PM schrieb Cristián Maureira-Fredes:

Hey folks,

thanks to a couple of people, we noticed that 6.2.2 had a really ugly
issue, that made the help() function unusable.

We know most of you knows the Qt API by heart ;)
but in any case, we didn't want to keep all the people
that usually rely on the help() function hanging...
so we decided to do an emergency release.

6.2.2.1 is out now on PyPi,
and to get that, you need to only run a:

    pip install -U pyside6

for people that pinned 6.2.2 as version,
it should resolve the latest from 6.2.2 releases
and in this case it will be 6.2.2.1

Sorry for the inconvenience,
and we thank the couple of reporters that filed
and issue on this specific topic.

We encourage you to give it a try,
so you can let us know if something's not properly
working: https://bugreports.qt.io/projects/PYSIDE

Have a nice Thursday!
Cheers


On 12/3/21 15:34, Cristián Maureira-Fredes wrote:

Hello everyone,

It took us a couple of extra days do our release
due some last minute issues with out wheels, but
we are happy to announce that 6.2.2 is out :)

You can find the changes here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.2.2 


(Please note, that we moved the changelogs from the 'dist/' directory
to the 'doc/changelogs/' directory)

For our macOS users,
we finally have Apple Silicon support,
so you can use PySide and Shiboken on your M1 computers ;)
Because we add support in the middle of a minor release,
we kindly ask you to report anything you found, so we can
tackle the issues before 6.3.

Besides the usual bug fixing,
we do have many new examples and improvements
on the QML side of things, for example
you can use the QmlUncreatable and QmlSingleton
decorators to declare your types.
Additionally, we noticed we didn't have the QtQuick3D
module exposed, so it's available as well.

Let's know if you find something that's not working
by opening a report on JIRA: https://bugreports.qt.io/projects/PYSIDE

Have a nice weekend!

Cheers




___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Qt for Python release: 6.2.2 is out!

[Cristián Maureira-Fredes]

Hey folks,

thanks to a couple of people, we noticed that 6.2.2 had a really ugly
issue, that made the help() function unusable.

We know most of you knows the Qt API by heart ;)
but in any case, we didn't want to keep all the people
that usually rely on the help() function hanging...
so we decided to do an emergency release.

6.2.2.1 is out now on PyPi,
and to get that, you need to only run a:

pip install -U pyside6

for people that pinned 6.2.2 as version,
it should resolve the latest from 6.2.2 releases
and in this case it will be 6.2.2.1

Sorry for the inconvenience,
and we thank the couple of reporters that filed
and issue on this specific topic.

We encourage you to give it a try,
so you can let us know if something's not properly
working: https://bugreports.qt.io/projects/PYSIDE

Have a nice Thursday!
Cheers


On 12/3/21 15:34, Cristián Maureira-Fredes wrote:

Hello everyone,

It took us a couple of extra days do our release
due some last minute issues with out wheels, but
we are happy to announce that 6.2.2 is out :)

You can find the changes here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.2.2 


(Please note, that we moved the changelogs from the 'dist/' directory
to the 'doc/changelogs/' directory)

For our macOS users,
we finally have Apple Silicon support,
so you can use PySide and Shiboken on your M1 computers ;)
Because we add support in the middle of a minor release,
we kindly ask you to report anything you found, so we can
tackle the issues before 6.3.

Besides the usual bug fixing,
we do have many new examples and improvements
on the QML side of things, for example
you can use the QmlUncreatable and QmlSingleton
decorators to declare your types.
Additionally, we noticed we didn't have the QtQuick3D
module exposed, so it's available as well.

Let's know if you find something that's not working
by opening a report on JIRA: https://bugreports.qt.io/projects/PYSIDE

Have a nice weekend!

Cheers


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.2.2 is out!

[Cristián Maureira-Fredes]

Hello everyone,

It took us a couple of extra days do our release
due some last minute issues with out wheels, but
we are happy to announce that 6.2.2 is out :)

You can find the changes here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/doc/changelogs/changes-6.2.2
(Please note, that we moved the changelogs from the 'dist/' directory
to the 'doc/changelogs/' directory)

For our macOS users,
we finally have Apple Silicon support,
so you can use PySide and Shiboken on your M1 computers ;)
Because we add support in the middle of a minor release,
we kindly ask you to report anything you found, so we can
tackle the issues before 6.3.

Besides the usual bug fixing,
we do have many new examples and improvements
on the QML side of things, for example
you can use the QmlUncreatable and QmlSingleton
decorators to declare your types.
Additionally, we noticed we didn't have the QtQuick3D
module exposed, so it's available as well.

Let's know if you find something that's not working
by opening a report on JIRA: https://bugreports.qt.io/projects/PYSIDE

Have a nice weekend!

Cheers
--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Unable to launch Qt Designer.exe bundled with the latest PySide6 on Win7 64bit

[Cristián Maureira-Fredes]

On 11/30/21 06:33, Zhao Lee wrote:
Unable to launch Qt Designer.exe bundled with the latest PySide6 on Win7 
64bit，Python  3.8




Hello Zhao,

You need to use `pyside6-designer`
not the Qt binary itself.

But additionally,
keep in mind Windows 7 is not a supported
platform in Qt 6.2
https://doc.qt.io/qt-6/supported-platforms.html#windows

Let's know how it goes!
Cheers




PS: In case you want to open a bug report, please use
https://bugreports.qt.io/projects/PYSIDE


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.2.1 is out!

[Cristián Maureira-Fredes]

Hello everyone,

In case you didn't notice,
yesterday Qt 6.2.1 was released,
and it was the same for Qt for Python :)

As always,
you can find the changelog here:

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-6.2.1

Let's know if you find something that's not working
by opening a report on JIRA: https://bugreports.qt.io/projects/PYSIDE

We are really thankful for the people that's participating
in Hacktoberfest and managed to port a couple of new examples
to the repository :D

Cannot spoil too many things,
but cool things are being prepared for 6.3
stay tuned!

Cheers


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] New Qt for Python release: 6.2.0 is out !

[Cristián Maureira-Fredes]

On 9/30/21 16:06, Cristián Maureira-Fredes wrote:

Dear Community,



# About the Installation

[snip]
Windows users however, can still run 'pip install pyside6'
to get 6.2.0

but Linux and macOS users need to install it from Qt servers:

pip install pyside6 \
   --index-url=http://download.qt.io/official_releases/QtForPython \
   --trusted-host download.qt.io

As soon as we have green light from the PyPi team,
we will let you know https://github.com/pypa/pypi-support/issues/1342
We are sorry for this issue.
[snip]


It's solved now, you should be able to run 'pip install pyside6' on 
Linux and macOS and get 6.2.0


Cheers!

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] New Qt for Python release: 6.2.0 is out !

[Cristián Maureira-Fredes]

On 10/4/21 16:38, Chris Hills wrote:

On 30/09/2021 15:06, Cristián Maureira-Fredes wrote:
 >
 > We hope you enjoy 6.2!
 >
 > Cheers

Thanks, Cristián!

As this does not include the Qt 6.2 libraries, is there a recommended 
way to install them on a RHEL 8 derivative?


Regards,

Chris Hills


Hey Chris,

not sure what are you referring to.
The wheel does include the Qt libraries,
so running a 'pip install pyside6' will get them for you
inside the virtual environment (recommended environment).

If you maybe are referring to the pyside6 OS package,
then I guess we could rely on a maintainer of such OS,
pretty sure we have some :)

(As Richard did already!)


Cheers

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] New Qt for Python release: 6.2.0 is out !

[Cristián Maureira-Fredes]

On 9/30/21 17:01, Florian Bruhin wrote:

Hey,

On Thu, Sep 30, 2021 at 04:06:55PM +0200, Cristián Maureira-Fredes wrote:

pip install pyside6 \
   --index-url=http://download.qt.io/official_releases/QtForPython \
   --trusted-host download.qt.io


I'd suggest this instead:

pip install pyside6 \
   --index-url=https://download.qt.io/official_releases/QtForPython

This way, there's no insecure connection (which would let someone in a
privileged network position inject code to run on your machine), and
thus also no --trusted-host override is needed.

Florian




Thanks Florian! :)

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] New Qt for Python release: 6.2.0 is out !

[Cristián Maureira-Fredes]

On 9/30/21 16:06, Cristián Maureira-Fredes wrote:

Dear Community,

- Shiboken has not a new feature called Opaque Containers, to avoid
   copying C++ containers into Python to use them.


(little typo)

Shiboken has now a new feature called Opaque Containers, to avoid
copying C++ containers into Python to use them.

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] New Qt for Python release: 6.2.0 is out !

[Cristián Maureira-Fredes]

Dear Community,

we are really happy to let you know that 6.2.0 is finally out.
The whole team worked really hard on this release, due to all
the changes related to Qt/C++ 6.2, which included re-adding new
modules, catching up with the latest Qt changes, adding new
modules, and on top of that, thinking of features that could
improve both the PySide and Shiboken experience.

We would have loved to be compatible with Apple M1 devices,
but we need more time to finish all the issues we have
discovered with the initial attempts.

A blog post with more details on the new features will be publish
in the following days, so stay tuned https://qt.io/blog


# About the Installation

Due the inclusion of more modules (including QtWebEngine),
and the Qt libraries for macOS that are now compatible with universal 
binaries, the size of the wheels increased, reaching the limit

we had on PyPi, so sadly it's not possible yet
to just run "pip install pyside6" for Linux and macOS users.

Windows users however, can still run 'pip install pyside6'
to get 6.2.0

but Linux and macOS users need to install it from Qt servers:

pip install pyside6 \
  --index-url=http://download.qt.io/official_releases/QtForPython \
  --trusted-host download.qt.io

As soon as we have green light from the PyPi team,
we will let you know https://github.com/pypa/pypi-support/issues/1342
We are sorry for this issue.


# About the changes

You can find the changelog here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-6.2.0

There are many bug fixes compared to previous releases,
but also a couple of nice changes, in summary:

- New examples, tutorials, and videos were added
  https://doc.qt.io/qtforpython-6/
- Even if it's not released yet, we are compatible with Python 3.10rc2
- The modules QtDBus, QtNetworkAuth, and QtBluetooth were added.
- Shiboken has not a new feature called Opaque Containers, to avoid
  copying C++ containers into Python to use them.
- The PyPy compatibility is half way there, but we will need more time.
- You can use 'qtpaths' not instead of 'qmake' when building PySide from 
source

- We added support for std::function for a couple of QThreadPool methods
- New QML functions were added, and it's now possible to use 
QmlRegisterSingletonInstance as well.




As always, give us a hand by reporting bugs, asking for new examples, 
tutorials, videos, etc on JIRA https://bugreports.qt.io/projects/PYSIDE


and drop by our community platforms in
https://wiki.qt.io/Qt_for_Python#Community

We hope you enjoy 6.2!

Cheers


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 6.1.3 released

[Cristián Maureira-Fredes]

Hey everyone :)

It took us an extra day this time,
but we are happy to inform you that 6.1.3 is out!
You can get it as:

pip install pyside6

or update your current installation via

pip install pyside6 -U

The changes can be found here
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-6.1.3

Remember to let us know if you find any issue with this release
by opening an issue on JIRA:
https://bugreports.qt.io/projects/PYSIDE

Keep in mind this is the last bug-fix release in 6.1,
and by the end of this month we expect to release 6.2 ;D

Drop by our platforms in case you are still suffering
by a bug we could prioritize before 6.2 is out

https://wiki.qt.io/Qt_for_Python#Community

or let us know any feedback regarding the documentation
https://doc.qt.io/qtforpython so we can improve them in time,
maybe a new tutorial? maybe additional explanation?


Have a nice weekend!

Cheers


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] PySide6 true_property

[Cristián Maureira-Fredes]

On 8/9/21 5:07 PM, pa...@paolodestefani.it wrote:

Hello list
I'm new to pyside but i played a lot with pyqt5 in the last few years.
I'm trying to port to pyside6 a simple application using snake_case and 
true_property new options


But I immediately got stuck in this simple problem: how to set the 
geometry of a widget ?
Before i used widget.setGeometry(10, 10, 50, 50) but how to do this with 
true_property ?


from PySide6.QtWidgets import QApplication, QWidget
from PySide6 import QtCore
from __feature__ import true_property
app = QApplication([])
w = QWidget()
w.geometry = 10, 10, 50, 50
Traceback (most recent call last):
   Python Shell, prompt 6, line 1
builtins.TypeError: 'PySide6.QtWidgets.QWidget.geometry.fset' called 
with wrong argument types:

   PySide6.QtWidgets.QWidget.geometry.fset(tuple)
Supported signatures:
   PySide6.QtWidgets.QWidget.geometry.fset(PySide6.QtCore.QRect)
   PySide6.QtWidgets.QWidget.geometry.fset(int, int, int, int)

How can i use the second sopported signature if not passing a tuple ?

--
Paolo De Stefani



Hey Paolo,

the issue lies on the nature of the setGeometry(x, y, w, h) function,
since it's just an overload that inside the code calls:
setGeometry(QtCore.QRect(x, y, w, h)), so it was designed
just for convenience.

The 'geometry' property *is* a QRect element,
so that's why one cannot assign a tuple, but a QRect object,
so for your specific case, you need to replace

>>> w.geometry = 10, 10, 50, 50

by

>>> w.geometry = QtCore.QRect(10, 10, 50, 50)

It doesn't sound too convenient,
but sadly it's the origin of the property itself,
which depends on a QRect element.

If you believe that accepting a tuple as a value
for the 'geometry' property is a valid use case,
that has even some positive effect in other sides
of PySide, feel free to open an issue on JIRA
https://bugreports.qt.io/projects/PYSIDE
so we can discuss on how difficult would it be
to implement and adapt the current bindings
for that use case.

Cheers!

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Porting to PySide6

[Cristián Maureira-Fredes]

Hey Christoph,

On 7/18/21 2:12 PM, ic...@gmx.net wrote:

Hi,

while porting to PySide6 I stumbled over this statement in the Qt docs:

"""

QAction, QActionGroup

These classes have been moved into the QtGui 
<https://doc.qt.io/qt-6/qtgui-module.html> module. Member functions that 
depend on types defined in QtWidgets 
<https://doc.qt.io/qt-6/qtwidgets-module.html> (such as QAction::menu() 
and QAction::setMenu()) are implemented as templates that will be 
instantiated only when called.


"""

It seems that the menu() function is not available in PySide6, is this 
correct? Is there a workaround for this missing functionality, or a plan 
when it will be added? I've read nothing about this in the porting 
section of PySide6.


Thanks for bringing this up, after the changes in QAction*
we didn't notice we would be missing those methods.

The short answer is:
we would see how we can handle this special case,
since it require more thinking on the binding generations side of things.

The long answer:

Due to the changes in QAction (moved from Widgets to Gui)
we have the case where classes are forward declared (in C++),
this can be workaround with shiboken declaring custom-types
with the names of the required types.
In the past, we used this trick with classes in QtMultimediaWidgets
that were used as arguments in functions in QtMultimedia,
so we were able to forward declare them, and they were recognized.

The problem here is that we don't only need to know the QMenu type,
but also we need to handle that type, because the functions
setMenu(QObject*) and menu() needs to be manually added on the 
typesystem (mainly because we don't have the ability to enable

them at instance time), and then we need to property convert
QMenu form C++ to Python, knowing more than the type name (which is
what we get with the forward declaration).

We might address this by writing helper functions, that somehow handle
the special situation, but I'm not sure if it's possible without
too many hacks.




Best Regards

Christoph



Cheers

PS: It might be worth opening a bug report, so we can continue
the discussion over there.

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 6.1.2 released!

[Cristián Maureira-Fredes]

Hey everyone,

Qt 6.1.2 was released, and Qt for Python too!

Check the latest release with:
pip install -U pyside6  # to update
or
pip install pyside6  # to install


Check the changes here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-6.1.2

Besides adding many missing classes, and fixing some bugs,
we continued improving the docs with more tutorial information
and the example gallery: https://doc.qt.io/qtforpython


If something is not properly
working, please let us know on JIRA, by opening a new report:
https://bugreports.qt.io/projects/PYSIDE

Thanks,
and have a nice Friday and weekend!

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Is Pyside 5.11 safe to use with Qt 5.15.2?

[Cristián Maureira-Fredes]

Hey Olivier,

On 6/14/21 10:47 AM, Olivier B. wrote:
I have been having trouble building Pyside 5.15.2. On windows, python 
3.5.2 crashes during the build, and on linux, i get another build error. 
I will eventually look into those errors, but would like to know if in 
the meantime i can safely use pyside 5.11 with qt 5.15?


PySide 5.15 is compatible with Python 2.7, and 3.5+
so it would be better for you to file a bug report,
and communicate the error so it can be solved or workaround.

Keep in mind that PySide was officially released in 5.12,
so on paper, you can take that as the initial stable version.
The path from there on was mainly to catch with missing API
and properly handling of Python's GIL,
so I would *highly recommend* you use 5.15.x


The context of usage is:
An application built with qt 5.15.2 that calls the python interpreter 
using python libraries. Pyside 5.11 is installed in the modules 
accessible by that application, excluding Qt dlls and plugins, so the 
ones of Qt 5.15 used by the process are used. The uses of pyside in the 
app are mostly to be used as a backend to draw matplotlib curves, and 
some little usage for displaying simple dialogs. it seems to work, but 
is there some hidden thing that could be problematic? 


If PySide 5.11 is installed...
was that built? or installed via pip?
it seems risky to play with that, but if it works at the moment,
and you cannot fix your build problems, I guess you can keep doing it,
but as mentioned before, there were some major issues that we fix in 
5.14.2, and are included in the following versions.


We usually recommend people to use the same Qt and PySide versions,
because at least with that we guarantee there will be no issues.

Cheers

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 6.1.1 released!

[Cristián Maureira-Fredes]

Hey everyone,

As you might have read on the development
mailing list or the official blog post,
6.1.1 was released this morning (CEST)
together with Qt/C++.

Remember to upgrade via: pip install -U pyside
or simple install the latest version with: pip install pyside

You can check the changes here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-6.1.1

If you nothing something that is not properly working,
please let us know on JIRA, by opening a new report:
https://bugreports.qt.io/projects/PYSIDE

Even thought we have many months before
the release of 6.2, it will be really nice if you can give
us a hand by testing your code with the latest PySide
release, in that case we can focus on fix as many bugs
as possible before the next minor release.
Due to module availability
we are expecting many users moving to PySide6
with that release version.

Thanks,
and have a nice week! :)

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] pylint and signal emit

[Cristián Maureira-Fredes]

On 5/31/21 1:29 PM, Ed Lipson wrote:
I'm using pylint on a program. It keeps pointing out an error of no emit 
member unless I disable the check.


self.dataChanged.emit(index, index) # pylint: disable=E1101

The code seems to work, so I am not sure if it is a false pylint error 
or it is working some other way, even though I have subclassed setData 
and as specified emitted dataChanged explicitly.

Could this be an artifact of the python/c++ nature of pyside?


Thanks,
Ed



Hey Ed,

most of the linters work mainly at a Python level,
and I expect them to fail when looking for Qt-inherited
members, which are usually not explicit.

In the case of a Signal,
we create that Python type with C-extensions,
so most of the behavior is manually written
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside6/libpyside/pysidesignal.cpp

There you can see that we create the "emit" method of  the type Signal
(line 177), so it should be picked up by autocomplete tools,
for example (in some IDE).

I'm not certain what's the process of pylint to detect the members,
but maybe you can ask the developers (or maybe on a public channel?)
to see what does they expect for the detection of members.

Do you have similar problems with Slots or Properties?

Cheers

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python release: 6.1 is out!

[Cristián Maureira-Fredes]

Hello everyone!,

We are really happy to announce that the 6.1
release of Qt for Python is finally out, and you can get it
with a simple:

pip install pyside6

It took us more time than usual, since we discovered
a couple of issues with some of the new experimental
features we were trying out, that completely stopped
us to do a release on the same day, luckily they were
solved, and we were able to release :)

I wrote a blog post with many details and resources
of the release:
https://www.qt.io/blog/qt-for-python-6.1
I hope it's informative enough and you like it.

As always, you can check the changelog here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-6.1.0


This release includes a technical preview of a commercial tool,
the Shiboken Wizard, mainly because we wanted to improve
our commercial offering, so more people get motivated to
get a license.
We believe that adding "things on top" of our Open Source
offering is a good path to explore to make Qt for Python
a better option commercially speaking.


We want bring more nice features to PySide and Shiboken,
and for that we need your help with ideas and feedback
of the current release, so drop by any of our community
platforms and let us know!
https://wiki.qt.io/Qt_for_Python#Community

As always, if you find any issue,
please please please
file a bug report on JIRA:
https://wiki.qt.io/Qt_for_Python/Reporting_Bugs
that will be really useful!

Thanks for your time,
Cheers

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 6.0.4 released

[Cristián Maureira-Fredes]

Hello everyone!

We are happy to tell you that 6.0.4 is out
(on the same day as Qt yay!)
and you can get it already from PyPi:

pip install pyside6

or update your current installation

pip install -U pyside6

You can check the summarized changelog in the following link
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-6.0.4

We are aiming to have everything in place for 6.1
during this week, so we expect a normal release in the following days.

Remember to let us know if you find any issue with this release
by opening an issue on JIRA:
https://bugreports.qt.io/projects/PYSIDE

If you are not already in some of our platforms,
remember to join the community:
https://wiki.qt.io/Qt_for_Python#Community

Cheers!

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] QAbstractTableModel headerData() Qt.BackgroundRole - Ignored?

[Cristián Maureira-Fredes]

Hello Ed,

I'd say the style-sheet reference
is the best place to find information
about "what to modify" regarding the styling:
https://doc.qt.io/qt-6/stylesheet-reference.html

from which you can see a link to:
https://doc.qt.io/qt-6/stylesheet-examples.html#customizing-qtableview
and
https://doc.qt.io/qt-6/stylesheet-examples.html#customizing-qheaderview

which highlights some of the options.

What you write there is QSS, which is similar to CSS,
maybe if you are not familiar to CSS it looks strange.

Were you referring to that with the C++ comment?

Cheers



On 4/12/21 1:29 PM, Ed Lipson wrote:


It worked, colored both Horizontal and Vertical headers.

I would have made the assumption that the section keyword would refer to 
a column/row of the header. Clearly it refers to the whole header. Where 
would I find documentation regarding this? If I wanted just the 
Horizontal header to be colored, for example. I did not see anything in 
the QHeaderView or QAbstractItemView documentation for just the section 
keyword.


Is there any doc on the syntactic sugar of passing in what appears (to 
me) to be a C++ string?


Thanks,
Ed


On Sun, Apr 11, 2021 at 6:03 PM Cristián Maureira-Fredes 
mailto:cristian.maureira-fre...@qt.io>> 
wrote:


Hello,

Nothing to worry about C++,
if you have a QTableView object, you can just use:

.setStyleSheet("QHeaderView::section{background-color: green;}")

on the object.

For example,
modifying the example:


https://code.qt.io/cgit/pyside/pyside-setup.git/tree/examples/widgets/itemviews/addressbook

<https://code.qt.io/cgit/pyside/pyside-setup.git/tree/examples/widgets/itemviews/addressbook>

Precisely the "addreswidget.py" file, adding the same line
under the declaration "tableView = QTableView()"

Produces:

https://imgur.com/a/iWo5rdM <https://imgur.com/a/iWo5rdM>


Cheers


PS: There is a small tutorial regarding stylesheet on the docs:
https://doc.qt.io/qtforpython/tutorials/basictutorial/widgetstyling.html
<https://doc.qt.io/qtforpython/tutorials/basictutorial/widgetstyling.html>

On 4/9/21 10:23 PM, Ed Lipson wrote:
 > I tried
 >
- self.my_tableView.horizontalHeader().setStyleSheet("background-color:
 > gray"), no effect. I get a little lost with the c++ to python
 > translations. I tried ("{background-color: gray;}") too and that
did not
 > work either.
 >
 > I saw a post about using a QPalette, but I'm not sure how that would
 > help or be applied.
 >
 > Thanks,
 > Ed
 >
 >
 > On Fri, Apr 9, 2021 at 3:43 PM Ed Lipson mailto:edlipso...@gmail.com>
 > <mailto:edlipso...@gmail.com <mailto:edlipso...@gmail.com>>> wrote:
 >
 >     Then why would there be a background role call to the headerData
 >     method? I'll give the stylesheet a try. Maybe I can
understand it.
 >
 >     Thanks,
 >     Ed
 >
 >
 >     On Fri, Apr 9, 2021 at 8:04 AM Hans Jörg Maurer
mailto:h...@pmeonline.net>
 >     <mailto:h...@pmeonline.net <mailto:h...@pmeonline.net>>> wrote:
 >
 >         I think you have to use
 >
 >         .setStyleSheet(QHeaderView:section{background - color:
green})
 >         Take a look at
https://doc.qt.io/archives/qt-5.9/stylesheet.html
<https://doc.qt.io/archives/qt-5.9/stylesheet.html>
 >         <https://doc.qt.io/archives/qt-5.9/stylesheet.html
<https://doc.qt.io/archives/qt-5.9/stylesheet.html>>
 >
 >         Regards
 >         Hans
 >
 >
 >
 >         Am Freitag, den 09.04.2021 um 13:29 schrieb Ed Lipson:
 >
 >             How would one set the background color of the QTableView
 >             (QtHorizontal orientation) header? I have tried the 'mail
 >             title' action, where I see the role being used. I
just don't
 >             get the color.
 >
 >             I used the same concept in data() and the cells take
on the
 >             background color as appropriate for the state.
 >
 >             PySide2 5.15.2 Python3.9.1
 >
 >             Thanks,
 >             Ed
 >
 >             PS: Where is it appropriate to ask such questions?
JIRA does
 >             not have a question type defined and doing it there
may be
 >             too much noise in the bug tracking system.
 >
 >
 > ___
 > PySide mailing list
 > PySide@qt-project.org <mailto:PySide@qt-project.org>
 > https://lists.qt-project.org/lis

Re: [PySide] QAbstractTableModel headerData() Qt.BackgroundRole - Ignored?

[Cristián Maureira-Fredes]

Hello,

Nothing to worry about C++,
if you have a QTableView object, you can just use:

.setStyleSheet("QHeaderView::section{background-color: green;}")

on the object.

For example,
modifying the example:

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/examples/widgets/itemviews/addressbook

Precisely the "addreswidget.py" file, adding the same line
under the declaration "tableView = QTableView()"

Produces:

https://imgur.com/a/iWo5rdM


Cheers


PS: There is a small tutorial regarding stylesheet on the docs:
https://doc.qt.io/qtforpython/tutorials/basictutorial/widgetstyling.html

On 4/9/21 10:23 PM, Ed Lipson wrote:
I tried 
- self.my_tableView.horizontalHeader().setStyleSheet("background-color: 
gray"), no effect. I get a little lost with the c++ to python 
translations. I tried ("{background-color: gray;}") too and that did not 
work either.


I saw a post about using a QPalette, but I'm not sure how that would 
help or be applied.


Thanks,
Ed


On Fri, Apr 9, 2021 at 3:43 PM Ed Lipson <mailto:edlipso...@gmail.com>> wrote:


Then why would there be a background role call to the headerData
method? I'll give the stylesheet a try. Maybe I can understand it.

Thanks,
Ed


On Fri, Apr 9, 2021 at 8:04 AM Hans Jörg Maurer mailto:h...@pmeonline.net>> wrote:

I think you have to use

.setStyleSheet(QHeaderView:section{background - color: green})
Take a look at https://doc.qt.io/archives/qt-5.9/stylesheet.html
<https://doc.qt.io/archives/qt-5.9/stylesheet.html>

Regards
Hans



Am Freitag, den 09.04.2021 um 13:29 schrieb Ed Lipson:

How would one set the background color of the QTableView
(QtHorizontal orientation) header? I have tried the 'mail
title' action, where I see the role being used. I just don't
get the color.

I used the same concept in data() and the cells take on the
background color as appropriate for the state.

PySide2 5.15.2 Python3.9.1

Thanks,
Ed

PS: Where is it appropriate to ask such questions? JIRA does
not have a question type defined and doing it there may be
too much noise in the bug tracking system.


___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside



--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 6.0.3 released!

[Cristián Maureira-Fredes]

Hey all!,

It took us some extra time,
but the new bug-fix release of 6.0 is finally out!

You can get 6.0.3 as always with:
pip install pyside6

or updating
pip install -U pyside6

You can check the details of the main
changes here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-6.0.3

We are focusing in 6.1 and 6.2 at the moment,
so let's know if there are any priority issues
in our JIRA, so we can try to fix them before
the next minor version releases:
https://bugreports.qt.io/projects/PYSIDE

Have a nice weekend!

Cheers


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] PySide6 Video

[Cristián Maureira-Fredes]

Hey Jason,

thanks for the feedback!

It seems there was a mistake with the uploaded video,
and in fact that's the faulty version that has a really long 
black-screen after the real talk.


(1) The audio is terrible too...I'm sorry about that,
but there should be related to being the faulty version.
The talk was recorded on a studio, so I would also expect a better audio
quality.

(2) Thanks! we will consider it for the next webinars/tutorials/talks

(3) Indeed there has been a lot of people contributing to the project,
not only with patches, but with constructive criticism and other ideas.
Still there is a lot of  things to do, to leave PySide as a proper 
member of the Python ecosystem, but hopefully we will be there soon.


(4) Sadly I don't have access to the videos,
but I can do offer the slides and demo-videos (no audio though)
on this link: http://maureira.xyz/qtforpython_qtws2020/

(5) No :(

(6) This is a critical topic. Maybe you remember some old emails
about threading, and some problems with the GIL. In a nutshell,
we required to completely revert the hold/release mechanism we
had in place for PySide https://bugreports.qt.io/browse/PYSIDE-803
and the whole team spent a lot of time doing so.

At the moment, if you look at QThread, for example, we have some
methods with an atribute 'allow-thread="yes"' on the typesystem,
which is releasing the GIL and get into a pure QThread call
(using Py_BEGIN_ALLOW_THREADS and Py_END_ALLOW_THREADS)
but as you can see, still we need to deal with the GIL. [1]

We could create a benchmark comparing a multiprocessing vs QThread
run, but I don't expect we will get numbers that are too different,
since there are still some bits of code implemented in C for the
multiprocessing module.

By any chance, do you have some benchmark in mind? or maybe
know a situation that could be cool to try out?

Cheers!


[1] 
https://doc.qt.io/qtforpython/shiboken6/typesystem_manipulating_objects.html?highlight=allow%20thread




On 3/3/21 4:47 AM, Jason H wrote:

I watched Qt/Christian's video at https://youtu.be/1ljPk7ZInRo about PySide6.

I have a few comments.
1. The audio is terrible, there's a lot of reverberation like it was filmed in 
a empty conference room, and a small one at that.
2. having the speaker inside with the slide is the entire screen is a huge 
visual improvement over previous Qt videos. Very nice to see!
3. I was very impressed with all the progress made towards making pyside a 
proper python community member.
4. The video seemingly ends at 26:54, But I continues silent and black for 
another hour and 4 minutes.
5. There's like a minute of green screen at the end. Easter egg? Doesn't seem 
like a Marvel post-credits scene...

6. The biggest caveat to using Python as I understand it is multi-threading. The python 
global interpreter lock requires use of the "multiprocessing module" however 
there is huge performance degradation as a result, whereas a QThread/QRunnable would be 
ideal. Is there a way to thread this needle and get concurrency through Qt?
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside


___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 6.0.2 released

[Cristián Maureira-Fredes]

Dear Community,

Qt for Python 6.0.2 is out!
As always you can get it through: pip install pyside6
or update it with a: pip install -U pyside6

You can read the changelog here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-6.0.2

Not many critical changes, but we are constantly polishing shiboken
and the generation of code, and documentation.
Additionally, there was a patch to properly handle boost headers
when generating bindings of code using it.

On the PySide aspect,
we have been pushing some updates to the documentation page
since the last release, and you might get more updates coming up soon.

Two highlights:

- We included a section for people new to Qt to clarify some concepts 
and details from Qt in: https://doc.qt.io/qtforpython/tutorials/index.html


- Due to the fact many people couldn't properly find the repository 
examples, we have a tool in place to show them here:

https://doc.qt.io/qtforpython/examples/index.html

More things will come!
And as always, please share with us your concerns,
findings, and comments in general:

https://bugreports.qt.io/browse/PYSIDE
https://wiki.qt.io/Qt_for_Python#Community


Cheers
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 6.0.1 released

[Cristián Maureira-Fredes]

Dear Community,

Qt for Python 6.0.1 is out!
As always you can get it through: pip install pyside6
or update it with a: pip install -U pyside6

You can read the changelog here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-6.0.1?h=6.0

It took us a day longer, since we had some issues
in our CI, but at least they are solved now :)

Even though this is a bug-fix release, we wanted
to address something that we were missing in 6.0.0,
the lack of Qt3D support and some plugins,
particularly imageformats, so now they are included
in the latest release.

We need your opinion!

We are trying to gather feedback from the '__feature__'
option we included from 5.15 and kept for 6.0
https://www.qt.io/blog/qt-for-python-6-released

If you have an idea to improve or complement the current
'snake_case' and 'true_property' options, let us know!
We would really like to keep adding more features on top
of PySide and Shiboken, to be much more than just
'Python bindings for Qt'.

Have a nice weekend!

Cheers

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 6.0.0 released

[Cristián Maureira-Fredes]

Dear Community,

We are really happy to tell you that 6.0.0 is finally out.

Some general information,
the project was renamed to PySide6 and Shiboken6 on PyPi,
to follow Qt versioning and avoid more confusion regarding
the name.


You can install it via: pip install pyside6


Keep in mind that not all the modules are available in Qt 6.0.0
but you can find a list here:
https://www.qt.io/blog/add-on-support-in-qt-6.0-and-beyond

We are still investigating how to distribute the new Qt Add-ons
but we will let you know ;)

You can find more information on the blog post:
https://www.qt.io/blog/qt-for-python-6-released

As always,
let us know if you find anything not properly working

https://bugreports.qt.io/projects/PYSIDE

and we would love to hear from you regarding  what's still missing:
* more tutorials?
* new functionality to the __feature__ option?
* different build options?
* new Python-only modules?

Remember that most of the features we adopt
come from the community ;)

Cheers


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Egg-info build problem on Fedora Linux

[Cristián Maureira-Fredes]

Hey Richard,

On 11/26/20 4:41 PM, Richard Shaw wrote:
I am working on updating the Fedora package, however, I've run into an 
issue.


I do a direct CMake build in order to properly enforce packaging 
requirements and build flags. I have been building the egginfo manually 
after the CMake build completes, however, several of the files are now 
CMake configuration files and are written to the BINARY dir instead of 
the SOURCE dir, and setuptools is unaware of this causing the 
egginfo build to fail.


I'm not sure "what changed" from previous versions,
IIRC nothing change regarding the build process,
and most of the things we are trying to do is a WIP
at the moment.

What's the last version you built using this approach?
and which one is the one giving you troubles?


Any hints on how to work around this?


I guess that your problem
is that you are mixing two approaches,
you either use CMake, or use the setuptools that we provide,
because in the second approach we take care of all the details
related caveats to do a proper Python build process.

So, I'd say you either use a:

cmake -B build path/to/pyside2 -DCMAKE_INSTALL_PREFIX=/some/path
cmake --build build
# Then an install to where you want to package it
# cmake --install build


or use the setuptools via

python setup.py install .



Thanks,
Richard



--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 5.15.2 released!

[Cristián Maureira-Fredes]

Hey everyone,

Maybe you noticed already,
but just wanted to let you know what we released Qt for Python 5.15.2
https://www.qt.io/blog/qt-5.15.2-released

You can find the change log here:
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-5.15.2?h=5.15

Please notice, that the projects that are generating bindings
for Qt-based code no longer need to include pyside2_global.h
for the property and signal/slot annotations to work.

If you find something that is not properly working,
please let us know on JIRA https://bugreports.qt.io/projects/PYSIDE

As always, remember you can reach the whole community
on this mailing list, but in many other platforms as well:
https://wiki.qt.io/Qt_for_Python#Community

Have a great weekend!

Cheers
--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Still struggling to build pyside2

[Cristián Maureira-Fredes]

Hey Filippo,

Since the submodule was removed in 'dev', that's why
it end up empty when you switch to the '5.15' branch, but you just
need to initialize it, look at these steps.

I hope it helps you,

Cheers


% git clone --recursive https://code.qt.io/pyside/pyside-setup
Cloning into 'pyside-setup'...
remote: Counting objects: 67731, done.
remote: Compressing objects: 100% (18501/18501), done.
remote: Total 67731 (delta 52307), reused 63081 (delta 47762)
Receiving objects: 100% (67731/67731), 22.05 MiB | 22.99 MiB/s, done.
Resolving deltas: 100% (52307/52307), done.

% cd pyside-setup

% git co 5.15
Branch '5.15' set up to track remote branch '5.15' from 'origin'.
Switched to a new branch '5.15'

% ls sources/pyside2-tools

% git submodule update --init
Submodule 'sources/pyside2-tools' 
(https://code.qt.io/pyside/pyside-tools.git) registered for path 
'sources/pyside2-tools'

Cloning into '/home/cmaureir/tmp/pyside-setup/sources/pyside2-tools'...
Submodule path 'sources/pyside2-tools': checked out 
'a8448837204faee0b457d1e2d4cbf574a284'


% ls sources/pyside2-tools
pylupdate/  tests/  CMakeLists.txt  LICENSE-lupdate  LICENSE-rcc 
LICENSE-uic  README.md  cmake_uninstall.cmake  pyside_tool.py* 
qt_attribution.json



On 11/19/20 10:30 AM, Filippo Rusconi via PySide wrote:

Greetings, fellow developers,

in my relentless quest of Python bindings for my software I am 
struggling to

build Pyside2/Shiboken2 according to this page:

https://doc.qt.io/qtforpython/gettingstarted-linux.html

I set up all my build tools to point to clang/clang++.

Then I cloned:

git clone --recursive https://code.qt.io/pyside/pyside-setup

And found that the sources directory had this content:

     cmake_helpers  patchelf  pyside6  pyside-tools  shiboken6

The sources/pyside-tools directory contained these two files:

     CMakeLists.txt  pyside_tool.py

Then I checked out 5.15:

     git checkout 5.15

And discovered that pyside-tools became pyside2-tools and is now empty.

I tried to find the contents of pyside2-tools on the web, but I could not.

At https://code.qt.io/cgit/pyside/pyside-setup.git/, branch 5.15, 
looking at the

source tree, I see
https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources?h=5.15, but 
the
sources directory contains sources/pyside2-tools @ a844883, which, when 
clicked

is an Invalid commit reference: a8448837204faee0b457d1e2d4cbf574a284.

Where can I find a source tree that actually contains something for
pyside-setup/sources/pyside2-tools ?

Thank you,

Filippo



--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Build error with Python 3.10

[Cristián Maureira-Fredes]

Thanks for keeping us posted Richard!
It seemed like a sensible change anyways...
and we have around 175 lines where we use it :S

Let's know if you discover something else.

Cheers!

On 11/18/20 10:42 PM, Richard Shaw wrote:

Ok, for now it looks like the change has been reverted in Python.

Thanks,
Richard

___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside



--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] QMYSQL

[Cristián Maureira-Fredes]

Hello Angelo,

Here is the documentation on how to use QMYSQL

https://doc.qt.io/qt-5/sql-driver.html#qmysql

In summary, you need to build the plugin from qtbase,
and build pyside from source since we don't package that plugin with
PySide.
As you might have read, the only plugins we provide
are QSQLITE, QPSQL, and QODBC.

Cheers

On 10/25/20 6:33 PM, Angelo Ballabio wrote:
When I create a virtual environment and loaded PySide2 into it, I 
realized that I cannot access MySQL database through 
QSqlDatabase.addDatabase("QMYSQL"), checking I saw that the 
libsqlmysql.so driver is not present in the sqldrivers directory along 
with the others. I tried to search the internet for the file in 
question, and nothing on the qt.io <http://qt.io/> website, and also on 
mysql.com <http://mysql.com/> I can't find the file. if i use the one 
installed in my ubuntu 20.10 distribution it tells me that it is not 
compatible with the others. In a standard environment its does. Anyone 
have a solution to suggest?


Angelo

___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside



--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Shiboken and Swift

[Cristián Maureira-Fredes]

Hey Jason,


On 10/19/20 3:11 PM, Jason H wrote:

So as it turns out, Swift allows for interop with C ( 
https://developer.apple.com/documentation/swift/swift_standard_library/c_interoperability
 ). C++ is not high on the list of Swift enhancements, but it's been requested, 
however there is no timeline or commitment.

1. There is some risk that in the future Apple releases a Swift-only library 
for a desirable feature.
2. There is the immediate situation that Swift is just better code than 
Objective-C and the code examples are more plentiful online and there is some 
value of being able to use Swift today.

Given those two factors, my question is if Shiboken could be adapted to 
auto-generate the C++/C, C/Swift bindings to be able to use Swift in a Qt 
project?


Without going into too much history,
Shiboken was originally inspired on the generator behind Qt Jambi,
so it would be possible to extend or change the functionallity
to support other languages.

The main issue, is that during the past years, Shiboken has been
modified and improved towards a better CPython code generation
and options to the typesystem has been added just to deal
with the ownership of object, Python's default variables,
etc.

I have no idea of Swift,
but I do believe it's certainly possible,
however there is no plans from the Qt for Python
project to extend it to other languages,
and I'd expect to get some contributions from the community
to make some aspects more "generic" or maybe improve
the possibility to include new languages.

If you would like to lead that effort,
maybe you could open a Suggestion or User story
on JIRA with some general ideas, suggestions,
material, motivation and more, so anyone could
take that as a starting point.

Cheers

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Failing build with newly-compiled PySide2 5.15.1

[Cristián Maureira-Fredes]

On 10/14/20 5:21 PM, Stephen Morris wrote:

On 10/14/20 12:45 PM, Cristián Maureira-Fredes wrote:


On 10/14/20 1:35 PM, Stephen Morris wrote:


On 10/14/20 12:05 PM, Cristián Maureira-Fredes wrote:



On 10/12/20 1:14 PM, Stephen Morris wrote:

[snip]


Hello,



Can you try to use a newer libclang?
There are some pre-built packages on
http://download.qt.io/development_releases/prebuilt/libclang/
that you can unzip, then point the LLVM_INSTALL_DIR variable to the directory.
Some people reported issues with 5.15 and libclang<=8 in other communication 
platforms, so it might be that.
On a side note, I really recommend you to try to move away from Python 2, since 
as you might know, it was deprecated [1], and we are completing removing Python 
2 support for Qt 6.


Thank you. I've rebuilt PySide using libclang.so.10 and now I get a different 
error message; I count this as progress, and I'll do a bit more investigation 
of my own before asking any further questions.



Thank you Stephen,
hopefully you can solve the issue soon.

Feel free to use a service like pastebin
to share the full log, so we don't miss any detail.

Cheers!


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Failing build with newly-compiled PySide2 5.15.1

[Cristián Maureira-Fredes]

On 10/14/20 1:35 PM, Stephen Morris wrote:



On 10/14/20 12:05 PM, Cristián Maureira-Fredes wrote:


On 10/12/20 1:14 PM, Stephen Morris wrote:

Following an apparently successful build of Qt 5.15.1 and PySide2
5.15.1 from source, I'm now attempting to compile the application
which I was previously compiling using version 5.12.5.

I get a slew of error messages involving PySide Properties:
[snip]
Thank you,
Stephen Morris.



Hello Stephen,

Can you please share which clang version, python version (including bug fix 
version), gcc version, and so on?
It really sounds there is a miss math issue, something seems to be off in your 
specific configuration.


Thank you Cristián.

I have:
libclang.so.8
   python 2.7.18 (newly built from source)
   gcc 8.3.1
... on a CentOS 7.8.2003 Linux system

My PySide and Shiboken libraries are newly-built from source (5.15.1) using 
Python 2.7.18 and Qt 5.15.1 (which was also built from source). In case it's at 
all relevant, Python was built using the -fno-semantic-interposition compiler 
flag and --default-symver linker flag.

Stephen.


Hello,

Can you try to use a newer libclang?
There are some pre-built packages on
http://download.qt.io/development_releases/prebuilt/libclang/
that you can unzip, then point the LLVM_INSTALL_DIR
variable to the directory.

Some people reported issues with 5.15 and libclang<=8
in other communication platforms, so it might be that.


On a side note, I really recommend you to try to move
away from Python 2, since as you might know,
it was deprecated [1], and we are completing removing
Python 2 support for Qt 6.

Cheers

[1] https://www.python.org/doc/sunset-python-2/


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Failing build with newly-compiled PySide2 5.15.1

[Cristián Maureira-Fredes]

On 10/12/20 1:14 PM, Stephen Morris wrote:
Following an apparently successful build of Qt 5.15.1 and PySide2 5.15.1 
from source, I'm now attempting to compile the application which I was 
previously compiling using version 5.12.5.


I get a slew of error messages involving PySide Properties:

[snip]

Thank you,
Stephen Morris.



Hello Stephen,

Can you please share which clang version,
python version (including bug fix version),
gcc version, and so on?
It really sounds there is a miss math issue,
something seems to be off in your specific configuration.

As a side note, you can always check the latest CI runs
like: 
https://testresults.qt.io/coin/integration/pyside/pyside-setup/tasks/1602656574


Where you can see the full logs, on the different platforms
including versions and everything.

Cheers!

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Failure trying to build pyside2

[Cristián Maureira-Fredes]

On 10/8/20 9:23 PM, Filippo Rusconi via PySide wrote:

Greetings, Fellow Developers,
[snip]
Has anybody experienced this kind of build failure ? What is the typical 
setup

that works for building pyside2 from source ?


For me it sounds like you are using a strange combination of
gcc and libclang, on one side, you have gcc 10
but a really old version of libclang 6.0,

could it be possible for you to download the prebuilt
libclang 10 from 
https://download.qt.io/development_releases/prebuilt/libclang/ and try 
again?





Sincerely,
Filippo Rusconi




Good Luck!


--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] 5.15.1 build error on Fedora Rawhide

[Cristián Maureira-Fredes]

strange,
that usually happens when you forget about adding an entry on the 
CMakeLists.txt, but checking it, it's there:


${QtCore_GEN_DIR}/qsocketdescriptor_wrapper.cpp

at least on 5.15
Can you check the src build files?

sources/pyside2/PySide2/QtCore/CMakeLists.txt

Cheers

On 9/10/20 4:26 PM, Richard Shaw wrote:
gmake[2]: *** No rule to make target 
'sources/pyside2/PySide2/QtCore/PySide2/QtCore/qsocketdescriptor_wrapper.cpp', 
needed by 
'sources/pyside2/PySide2/QtCore/CMakeFiles/QtCore.dir/PySide2/QtCore/qsocketdescriptor_wrapper.cpp.o'.  
Stop.


Ideas?

Full build log:

https://hobbes1069.fedorapeople.org/build.log

Thanks,
Richard

___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside



--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 5.15.1 released!

[Cristián Maureira-Fredes]

Dear Community,

we are really happy to let you know
that 5.15.1 is out!

https://pypi.org/project/PySide2/

As always, you can get it via PyPi
with a simple: "pip install pyside2"
or "pip install -U pyside2" to update :D


You can read the blog post that highlights
a couple of things, and one new feature
that we decided to include for 5.15 users
to avoid waiting until Qt6 ;)

https://www.qt.io/blog/qtforpython-5.15.1-released

Here is the changelog for a detailed
commit list:

https://code.qt.io/cgit/pyside/pyside-setup.git/tree/dist/changes-5.15.1?h=5.15

Thanks for your support,
and let's stay in touch: https://wiki.qt.io/Qt_for_Python#Community

Cheers


--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] python setup.py build fails with error: ‘class Shiboken::GilState’ has no member named ‘abandon’

[Cristián Maureira-Fredes]

Hello,


On 9/8/20 9:00 PM, Filippo Rusconi wrote:

Greetings, Fellow Developers,

[snip]


Could you please share the whole output log?
it would be really nice if you could share a pastebin link
or a similar service, since usually you can see a summary of the 
configuration before the building starts at the beginning.




Sure, this is what I got:

https://paste.debian.net/1163090/


I think that's the incorrect output,
since the original was Python 3.8
and the log is using Python 2.7
(which even though is supported, is already deprecated)

Not sure if debian includes 'venv' with he standard Python,
I think in ubuntu one need to install 'python-venv',
but anyway, can you try to do a small build, just to try:

python3 -m venv env
source env/bin/activate
python setup.py install --module-subset=Core --verbose-build # note that 
here is 'python' not 'python3' because the environment is activated.


so we only try to build QtCore.


The errors on the current build process is CMake complaining that cannot 
find Python3, since that was detected:


> -- Shiboken2Config: Using default python: .cpython-38-x86_64-linux-gnu
And looking at the rest of the error:

> 
/usr/lib/x86_64-linux-gnu/cmake/Shiboken2-5.15.0/Shiboken2Config.cpython-38


Seems like you have shiboken2 5.15 installed in your system,
maybe as a dependency?

In any case, creating the virtual environment,
and activating it will do the job of isolating
the build process, so we avoid picking up system stuff.


[sni]
Filippo


Good luck!
and keep up updated :)

Cheers

--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
--
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] python setup.py build fails with error: ‘class Shiboken::GilState’ has no member named ‘abandon’

[Cristián Maureira-Fredes]

Hello,

On 9/8/20 3:51 PM, Filippo Rusconi via PySide wrote:

Greetings, Fellow Developers,

new to this list, and new to the PySide2 world, I hope I am not erring by
sending this mail.

I am willing to explore the Qt for Python universe, and for that I am 
following

the instructions located at
https://doc.qt.io/qtforpython/gettingstarted-linux.html

I could perform all the steps up to the build of PySide2, with the 
following

command line:

python setup.py build --qmake=/usr/lib/qt5/bin/qmake --build-tests 
--ignore-git


The build configures fine and then the build stops with the following 
error:
[snip] 


Could you please share the whole output log?
it would be really nice if you could share a pastebin link
or a similar service, since usually you can see a summary of the 
configuration before the building starts at the beginning.




I do not yet know what GIL is. All I can say is that I had done:


It's the Global Interpreter Lock from Python,
in simple words, what controls how python code executes,
https://docs.python.org/3/glossary.html#term-global-interpreter-lock

Since PySide uses a C++-based library underneath,
we need to control the interaction with that lock,
acquiring it, and locking it, that's why there is some interaction
withing the binding generator tool, Shiboken.


git clone --recursive https://code.qt.io/pyside/pyside-setup
cd pyside-setup
git checkout 5.14

I checked out 5.14 because that is the version I have in my Debian box:
$ dpkg -l "qtbase5*"
||/ Name  Version   Architecture Description
+++-=-=--=== 

ii  qtbase5-dev:amd64 5.14.2+dfsg-6 amd64    Qt 5 base 
development files




That sounds correct,
since 5.14 was compiling and it's being currently used by many people,
although, we are currently on 5.15, but I guess you will get it 
eventually ;)


Any good soul would explain that error to me and hopefully allow me go 
forward ?


I'd say it might be due to Python incompatibility,
but it seems you are using 3.8, but anyways,
I would like to see the full log (until it fails).



Most sincerely,

Filippo



Cheers

--
Dr. Cristián Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Disabling OpenGL support in PySIde 5.13.2 when Qt 5.13.2 is built with -no-opengl

[Cristián Maureira-Fredes]

Hey Tom,

I already replied to your question on the other thread you asked
the same.

Let me copy paste here in case you didn't get it:

---
Hello Tom,

Sadly I don't have a solution for you
besides a manual intervention
of the CMakeLists.txt file on the QtGui module:
pyside-setup/sources/pyside2/PySide2/QtGui

If you comment the lines with OpenGL references
you should get many warning from the typesystem
of classes defined but not generated, for example
the line:



on the 'typesystem_gui_common.xml' file (on the same directory).

I believe it should build, but in case of other weird typesystem
errors, you will need to comment from the XML file
all the entries related to the classes you commented on the CMakeLists.txt.



The only options we have built-in are to skip certain modules:
--skip-modules=Widgets,WebEngine,...

and to build just some modules:
--module-subset=Core,Gui, ...

Sorry for the inconvenience,
but good luck with your effort!

Cheers
---

On 7/24/20 6:58 PM, Kacvinsky, Tom wrote:

Hi,

I am in a situation where I do not want OpenGL support in Qt5 5.13.2 (we don't 
use it, we
do not make a product that requires OpenGL support), so I configured Qt5 with 
-no-opengl.
However, PySide 5.13.2 seems to require OpenGL support for building the QtGui 
Python
module.  How can I disable that support considering Qt5 was built without 
OpenGL support?
The same goes for OpenSSL (though we are using that, so it was me muffing the 
build of Qt5
without OpenSSL support).

Thanks,

Tom

___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside



--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] OpenGL in Qt 5.13 and PySide 2 corresponding to it

[Cristián Maureira-Fredes]

Hello Tom,

Sadly I don't have a solution for you
besides a manual intervention
of the CMakeLists.txt file on the QtGui module:
pyside-setup/sources/pyside2/PySide2/QtGui

If you comment the lines with OpenGL references
you should get many warning from the typesystem
of classes defined but not generated, for example
the line:



on the 'typesystem_gui_common.xml' file (on the same directory).

I believe it should build, but in case of other weird typesystem
errors, you will need to comment from the XML file
all the entries related to the classes you commented on the CMakeLists.txt.



The only options we have built-in are to skip certain modules:
--skip-modules=Widgets,WebEngine,...

and to build just some modules:
--module-subset=Core,Gui, ...

Sorry for the inconvenience,
but good luck with your effort!

Cheers

On 7/15/20 8:07 PM, Kacvinsky, Tom wrote:

HI all,

Due to constraints we have, I need to build Qt5 on CentOS 5.  Yeah, I know, not 
ideal,
but there is nothing I can do about it for the moment.

In any case, Qt5 depends on OpenGL 2.0 or later, and CentOS 5 has OpenGL 1.2.  
So
I have been fighting to get a later version of Mesa built for CentOS 5, which 
would
give me the OpenGL 2.0 support I need.  I have not had much luck.

So, what I did is build Qt5 without OpenGL support (the -no-opengl configure 
flag)
and Qt5 builds just fine.

However, when I go to build PySide2, it fails to build the QtGui module due to 
missing
OpenGL based targets:

make[2]: *** No rule to make target 
`PySide2/QtGui/PySide2/QtGui/qabstractopenglfunctions_wrapper.cpp', needed by 
`PySide2/QtGui/CMak\
eFiles/QtGui.dir/PySide2/QtGui/qabstractopenglfunctions_wrapper.cpp.o'.  Stop.
make[1]: *** [PySide2/QtGui/CMakeFiles/QtGui.dir/all] Error 2

Is there a way of configuring PySide2 builds (via setup.py options) to get 
around the
building of OpenGL support in QtGui?

Thanks,

Tom

___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside



--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

[PySide] Qt for Python 5.14.2.3 released!

[Cristián Maureira-Fredes]

Hey everyone!,

We decided to proceed with another
release for 5.14.2, and now you can get
the .3 release :)

https://pypi.org/project/PySide2/5.14.2.3/

You can get it via: pip install pyside2==5.14.2.3

The reason was that we still had some important
bugs on 5.14.2.2, but you can read more in
the changelog:

https://code.qt.io/cgit/pyside/pyside-setup.git/commit/?h=5.14

The whole team is focusing on Qt6 compatibility
and features, so if nothing too serious is found in the latest
5.14 release, it will be the last one.

5.15.1 is around the corner, and should be out next month,
so hopefully you can give us a hand by reporting new issues
on 5.15.0, or helping us smashing some bugs!

https://bugreports.qt.io/projects/PYSIDE

A big thanks to the people that is contributing,
and keeping the community so active.
Remember that you can reach us on different platforms:

https://wiki.qt.io/Qt_for_Python#Community

Cheers!

--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

Re: [PySide] Important: 5.15.0 wheels (Windows 64bit) replaced

[Cristián Maureira-Fredes]

Hello everyone,

Thank you very much Christoph
to help us identify a last missing file
in the wheels.

A new set of Windows 64bit wheels has been uploaded now,
that solve the problem you raised.

Even if the name of the wheel has a '_2',
it will still be picked up when you write:

pip install pyside2==5.15.0

We encourage everyone to give it a try ;)

Thanks

On 6/15/20 5:10 PM, Cristián Maureira-Fredes wrote:

Hey Christoph,

Can you share more information on the bug report?
https://bugreports.qt.io/browse/PYSIDE-1323

Did you uninstall shiboken2 too when doing the re-install?

Cheers

On 6/15/20 4:55 PM, ic...@gmx.net wrote:

Hi Cristian,

I fear this is still not working for me. I just installed 5.15.0 into a
fresh virtual environment (it used
PySide2-5.15.0-5.15.0_1_cp35.cp36.cp37.cp38-none-win64.whl and the
corresponding shiboken2 package). Afterwards I got "ImportError: DLL
load failed: Das angegebene Modul wurde nicht gefunden" when importing
the QtCore module. Doing the same thing with PySide2-5.14.2.2 works as
expected.

Best Regards
Christoph

On 15.06.20 10:51, Cristián Maureira-Fredes wrote:

Hello everyone!,

We just updated the Windows (64bit) wheels on PyPi
due to a packaging problem.

Some users started to report a problem when trying

import PySide2


That looked like this:

PySide2/__init__.py: Unable to import shiboken2 from [snip]
  from .shiboken2 import *
ImportError: DLL load failed while importing shiboken2: The

specified > module could not be found.

It took us some time to check this,
because not everyone could reproduce, until finally
we figure out that it was due to a problematic DLL.

The issue is that the Qt CI was updated for 5.15.0
and we started to use MSVC 2019, hence we shipped
those DDLs (like vcruntime140.dll).

You can find the fixes for the situation in the following
patches:
https://codereview.qt-project.org/c/pyside/pyside-setup/+/303785
https://codereview.qt-project.org/c/pyside/pyside-setup/+/303914


Why it worked for some people?
Because having a 'newer' version of MSVC installed in your system
provided the missing DLL, so people with 2019 compatible
redistributable binaries, didn't see the issue.

Since this problem was affecting only Windows,
we decided to update only those wheels, that now contain a "_1"
in the name, so people will be able to install 5.15.0
and get the updated version.

If you already have 5.15.0 installed,
you will need to reinstall:

pip uninstall PySide2 # will uninstall 5.15.0
pip install PySide2 # will install 5.15.0_1



Thanks to all the people that helped us to figure out
the problem, and we invite you to join the different
platforms we have to be in touch with the community:
https://wiki.qt.io/Qt_for_Python#Community

Have a nice week!
Cheers





___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside





--
Dr. Cristian Maureira-Fredes
R&D Manager

The Qt Company GmbH
Erich-Thilo-Str. 10
D-12489 Berlin

Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin,
Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
___
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside