QtCS2021 - Qt for Python: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Category:QtCS2021 ==Session Summary== Let's talk about what can be improved in Qt for Python and how you can contribute ==Session Owners== * Friedemann Kleint (Friede...") |
(→Notes) |
||
Line 12: | Line 12: | ||
==Notes== | ==Notes== | ||
(Notes by CristianMaureira) | |||
[https://wiki.qt.io/Qt_for_Python_Akademy2020 Check the discussion on Akademy 2020] | |||
* Abstract layer to use PySide2 and PySide6, so people can use it seamesly. | |||
** https://github.com/mottosso/Qt.py | |||
** https://github.com/spyder-ide/qtpy | |||
* (Andreas) Expose Python in QML? | |||
** yeah, it's possible. | |||
* QtCreator | |||
** memory consumption too high. | |||
** lacking support... | |||
** Lacking warning messages from the LSP | |||
** Lacking code completion | |||
** Detection on the virtual environment. | |||
* Other IDEs | |||
** Sublime text with Anaconda package. | |||
** QtCreator uses a lot of GPU in old computers. | |||
* UI files | |||
** Get step by step tutorials on how to use it, | |||
** Don't fall into the C++ docs. | |||
* Cookiecutter templates | |||
* PyCharm | |||
** not the LSP, a commercial version. | |||
** Maybe we could improve LSP with Rope | |||
** Pylance | |||
** https://github.com/JetBrains/intellij-community/tree/master/python | |||
* Python Debugging story on QtCreator | |||
** Needs maintainer. | |||
* Feedback from Forums | |||
** PyQt5 -> PySide2 | |||
** Designer based UI missing tutorials. | |||
*** Modify design generated file. | |||
*** Performance (old) | |||
** Maybe connect to an API? | |||
* Other areas: Check VFX | |||
** https://www.rhino3d.com/ | |||
** https://vfxplatform.com/ | |||
* More tutorials on Python/C++ | |||
* Redirect | |||
** doc.qt.io/pyside -> qtforpython | |||
** doc.qt.io/pyside2 -> qtforpython-5 | |||
** doc.qt.io/shiboken | |||
** doc.qt.io/shiboken2 | |||
** ... | |||
Q: Doesn't that scripting example use a bunch of extra code | |||
referencing the Python C API instead of a nice Qt API? |
Revision as of 18:02, 22 June 2021
Session Summary
Let's talk about what can be improved in Qt for Python and how you can contribute
Session Owners
- Friedemann Kleint (Friedemann.Kleint@qt.io)
Notes
(Notes by CristianMaureira)
Check the discussion on Akademy 2020
- Abstract layer to use PySide2 and PySide6, so people can use it seamesly.
- (Andreas) Expose Python in QML?
- yeah, it's possible.
- QtCreator
- memory consumption too high.
- lacking support...
- Lacking warning messages from the LSP
- Lacking code completion
- Detection on the virtual environment.
- Other IDEs
- Sublime text with Anaconda package.
- QtCreator uses a lot of GPU in old computers.
- UI files
- Get step by step tutorials on how to use it,
- Don't fall into the C++ docs.
- Cookiecutter templates
- PyCharm
- not the LSP, a commercial version.
- Maybe we could improve LSP with Rope
- Pylance
- https://github.com/JetBrains/intellij-community/tree/master/python
- Python Debugging story on QtCreator
- Needs maintainer.
- Feedback from Forums
- PyQt5 -> PySide2
- Designer based UI missing tutorials.
- Modify design generated file.
- Performance (old)
- Maybe connect to an API?
- Other areas: Check VFX
- More tutorials on Python/C++
- Redirect
- doc.qt.io/pyside -> qtforpython
- doc.qt.io/pyside2 -> qtforpython-5
- doc.qt.io/shiboken
- doc.qt.io/shiboken2
- ...
Q: Doesn't that scripting example use a bunch of extra code referencing the Python C API instead of a nice Qt API?