Add documentation for methods or helpers that are specific to qtpy
See original GitHub issueThis includes documenting
from qtpy.QtCore import Signal, Slot
- The use of the openfiledialog openfolderdialog helpers (study the option of overloading QFileDialog… which would also need documentation as it would change the default behavior)
- Where to find the Qt version
from qtpy.QtCore import __version__
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
The Qt Help Framework - Qt for Python - Qt Documentation
Contains the table of contents, indices, and references to the actual documentation files (*.html). It also defines a unique namespace for the documentation....
Read more >Documenting Python Code: A Complete Guide
A complete guide to documenting Python code. Whether you're documenting a small script or a large project, whether you're a beginner or seasoned...
Read more >PyQtGraph's Helper Functions - Read the Docs
Qt uses the classes QColor, QPen, and QBrush to determine how to draw lines ... these functions directly–any function or method that accepts...
Read more >Using automatic documentation of my own function with Qt ...
What is this? Where is it documented? Can I use this to generate my own Qt Assistant qch help files or something?
Read more >qtpy/CHANGELOG.md at master · spyder-ide/qtpy - GitHub
... 61 - Add documentation for methods or helpers that are specific to qtpy ... PR 357 - PR: Add initial Methods, helpers...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Besides the things described at the OP probably some description for the env variables that
QtPy
uses (FORCE_QT_API
,QT_API
) as well as state variables available (PYQT5
,PYQT6
,PYSIDE2
,PYSIDE6
, etc) could be nice (also letting clear that we are trying to follow Qt5 layout for things, so for examplepyqtSlot
->Slot
)Yes, related in the sense that following what is decided there (keeping it as it is, adding aliases to those functions or patching
QFileDialog
) the documentation should reflect that@dalthviz I can try to help with this, but given I’m not a Qt expert (both a benefit and a downside when writing user docs), I’ll need a little more detail on what you want said here:
Signal
andSlot
from here, are there QtPy-specific syntax or semantics that need to be described, or something else we want to say?