Issue in /src/pages/guides/creating-python-plugin.md
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start with src/pages/guides/creating-python-plugin.md and review the custom_import.py example alongside the reported PySide2 and PySide6 imports. Confirm which import form is supported in the current Substance Painter version, then update the tutorial so the example loads without the reported import issue.
Written by the indexing model from the issue text.
Description
I was going over the "Creating a Python plugin" tutorial, and had issues running the custom_import.py plugin code. It seems that PySide 2 is not supported in the most recent version of Substance Painter.
Is the following more appropriate? While I still had errors after making this change, at least it loaded the plugin.
from PySide6 import QtWidgets
from PySide6.QtGui import QAction
- Dominant language
- HTML
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#167 ·
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·