Qt for Python/Reporting Bugs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (fixed minor typo and minor grammar issue) |
||
| Line 10: | Line 10: | ||
Here is a nutshell description of how to report a bug : | Here is a nutshell description of how to report a bug : | ||
# Visit [http://bugreports.qt.io/browse/PYSIDE | # Visit [http://bugreports.qt.io/browse/PYSIDE bugreports.qt.io/browse/PYSIDE]. | ||
# If you don't have a Qt account, you should create | # If you don't have a Qt account, you should create one (https://account.qt.io/). | ||
# Use the "Quick Search" field in the top right to try to find any similar bugs, some times there are related bugs that could be complementary to your issue. | # Use the "Quick Search" field in the top right to try to find any similar bugs, some times there are related bugs that could be complementary to your issue. | ||
#* Leave a comment with any additional info you have. | #* Leave a comment with any additional info you have. | ||
| Line 31: | Line 31: | ||
* If you encounter a missing binding, you also will encounter a Python error. | * If you encounter a missing binding, you also will encounter a Python error. | ||
* On the other hand, when there is no clear error message, but some method does not work, this still could be a Qt for Python issue, but also a Qt bug. | * On the other hand, when there is no clear error message, but some method does not work, this still could be a Qt for Python issue, but also a Qt bug. | ||
If it is not clear | If it is still not clear if your issue is from Qt or Qt for Python, please write a small Qt/C++ piece of code that can use the class/method you are having issues with, | ||
to see if the problem persist, if it does, it is a Qt bug. | to see if the problem persist, if it does, it is a Qt bug. | ||
Revision as of 20:28, 26 October 2018
Bugs in Qt for Python can be reported at the bug tracker.
The quality of the bug report can dramatically impact how likely it is that the bug will be fixed.
We follow the same criteria than any Qt related bug, check the Qt Reporting Bugs page for more information.
Step by step
Here is a nutshell description of how to report a bug :
- Visit bugreports.qt.io/browse/PYSIDE.
- If you don't have a Qt account, you should create one (https://account.qt.io/).
- Use the "Quick Search" field in the top right to try to find any similar bugs, some times there are related bugs that could be complementary to your issue.
- Leave a comment with any additional info you have.
- Click "Vote" — You will usually have a higher chance of having your bug fixed by voting on an already existing bug than creating a new one.
- Add yourself as a watcher, if you want to track the progress of the bug via email.
- If you don't find a bug report which matches your issue, then click "Create New Issues", and fill out the fields.
- Project: Qt for Python
- Type: Bug or Suggestion
- Component: Shiboken, Documentation or PySide
- Description: Provide a detailed description of the issue
- Environment: Write your current environment configuration, OS, Python version, PySide2 version, etc.
- Attachment: Please include a minimal reproducible script.
Considerations
It could be the case that your issue is not a Qt for Python bug, but a Qt one. Please be sure before submitting a bug.
- Normally, Qt for Python bugs could expose some issues with Python directly.
- If you encounter a missing binding, you also will encounter a Python error.
- On the other hand, when there is no clear error message, but some method does not work, this still could be a Qt for Python issue, but also a Qt bug.
If it is still not clear if your issue is from Qt or Qt for Python, please write a small Qt/C++ piece of code that can use the class/method you are having issues with, to see if the problem persist, if it does, it is a Qt bug.