Qt for Python

Yes, I also encountered that. Sadly, that's exactly what it means: PySide's asyncio event loop does not implement getaddrinfo: https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside6/PySide6/QtAsyncio/events.py#n552 In fact, none or almost none of the IO-related methods are implemented. Documentation also says that directly at https://doc.qt.io/qtforpython-6/PySide6/QtAsyncio/index.html: We consider that this API consists of two levels: Fundamental infrastructure for event loops and asynchronous operations, including futures, tasks, handles, executors, and event loop management functions (see below). A user-facing API for use in applications, including transports and protocols, network connections, servers, sockets, signals, subprocesses. QtAsyncio currently covers the first level.: One solution is to use trio in guest mode, like in this example: https://doc.qt.io/qtforpython-6/examples/example_async_minimal.html. Except it will not help you, because LangChain does not support trio. There are a few libraries that implement a similar capability for asyncio, but none of them seem particularly mature.

A truncation like "nRequestResponse" instead of "onRequestResponse" typically means the SLOT function is missing. Probably SLOT("onRequestResponse") needs to be specified in the connect statement ( see https://doc.qt.io/qtforpython-6/tutorials/basictutorial/signals_and_slots.html#tutorial-signals-and-slots ).

Ok, I better understand your issue. I am currently wondering whether QtAsyncio should have followed more closely that design.

It seems to me that the @QMLElement would be necessary to introduce new elements to QML. My problem is the communication between the ui.qml (only geometry, rectangles, buttons) from Qt Design Studio and the .qml (events, signals for buttons, radiobuttons,...) e.g. from Qt Creator. I don't know how to refer/connect the objects in ui.qml to/with the associated events in .qml, I guess. Button with id=button1 in ui.qml and on the other hand button1.onClicked in .qml, how can I address to button1 from ui.qml to qml?

The problem had been solved,my windows version does not match minimal requirements

Sorry I don't have a Windows machine at hand, I also tried on Linux with Python 3.13.5 and a fresh install of shiboken-generator (6.9.1 at the time of writing) and it all worked well. How did you setup Python on Windows ?

@jsulm Probably Project screenshot will also be helpful [image: a61b54a7-05a5-43fb-90bc-4f777306a77f.png]

Please try 6.9.1; 6.8 might be too old for that.

@wayfarer You're setting font size in setText - are you sure it is same as what was set before when elidedText was calculated? Regarding resizing the window: you will need to do these calculations again when the window is resized, currently you don't do that.

The chart example is an interesting starting point.

From the looks of it, it seems like having the animation available for both direction is the easy path.

Changes in enums types has come up several times on the PyQt mailing list. You might find a better answer there, or a fix if the behavior is unintentional.

There was a regression related to QGraphicsView in 6.9.1, https://bugreports.qt.io/browse/PYSIDE-3115 , this could be the reason. It will hopefully again work in 6.9.2.

@jeremy_k Oh I agree, and I am guessing that is what is happening. I am not a regular Python/PySide user, only occasional. At design time in the IDE I thought if you click on Qt.ItemFlag.ItemIsSelectable is takes you straight to an imported file where that is defined as a number in an enum. Which makes you (me) kind of think that can be done as a constant. But I suppose that is wishful thinking. Assuming the slow lookup is indeed required, it makes one reflect at just how many seemingly innocuous expressions, especially Qt ones, may be dotted around the code which could be in this situation and could be optimized if the coder happens to notice ad think about them. Which the OP may wish to look into if speed is such an issue.

Externally, no, but you can always follow the meeting notes: https://wiki.qt.io/Qt_for_Python_Development_Notes you can see iOS support is being actively investigated.

@ajitjohn said in Failed to install QT designer using Python 3.12.3 (URGENT HELP): install pyside6 which is supported in python latest versions . Once you installed it search for pyside6-designer.exe in your pc My path is C:\Users\user\AppData\Local\Programs\Python\Python312\Scripts\pyside6-designer.exe Side comment. Please try to use virtual environments, and avoid installing Python Packages system-wide. It's the number 1 problem when people report that 'a module' doesn't work on Python projects. In each project, you could have one by: $ cd my_project my_project $ python -m venv venv my_project $ venv\Scripts\activate.bat # for cmd my_project (venv) $ python my_project (venv) $ pip install pyside6 Now the Python and Pip you have there is tied to that local venv.

Similarly to what was discussed in https://forum.qt.io/topic/159077/moving-away-from-qt3d-is-qtquick3d-ready/2 I'd say you might need to evaluate if you can: Rely on QtRHI for a new rendering ad-hoc system Check if Qt Quick 3D is enough for your project. Because it's not tied anymore to the qt meta repo, we might face issues from the Qt for Python side of things, and we might stop providing it in newer versions. So far, it's present in 6.9, and hopefully we can provide it for 6.10. Like any piece of software, being deprecated since 6.8, Qt3D will not get new features, or might not have active development. I wouldn't expect for it to go completely away in 1-2 years, but it's highly probable that it might be fully replaced in a few years. This is only my 'feeling' and not what it will happen.

https://bugreports.qt.io/browse/QTBUG-137250