convert setup.py and related files to pyproject#132
convert setup.py and related files to pyproject#132hannesdelbeke merged 4 commits intotechartorg:masterfrom
Conversation
a7faa89 to
4a90b90
Compare
|
The reason for version mismatch is blender moved from addons to blender extensions. note that, since 1.4.2 is already released, we can not match this. |
|
i also like that we moved to |
|
since pyside6 is now a dependency, we can use the minimum version for python that pyside6 supports https://vfxplatform.com/ suggests python 3.11 or higher, and pyside 6, but i know blender an get funny about staying in line with the vfx platform. |
Support for old addon setup can only be dropped if the minimum version of the
I will add a note on this in this PR #136
vfxplatform is very useful however for our case here the python version we support should be indicated by the Blender version (which with Blender 4.2 would coincidentally be 3.11). |
|
Let me know which version of Blender you think we should be the lowest supported and I will update this PR |
|
blender 4.2 sounds good |
4a90b90 to
707732f
Compare
|
What's left on this is
If that works then this is good to merge. P.s. I will make a separate PR making 4.2 the minimum supported version. |
|
i'll just accept this PR and try release a package. |
Modernize the build files.
Some notes of interest.
["*.png", "*.qss"]but there are no files matching it - I removed these..svgfile within the ui folder was never included - I added this to be included.Which is the minimum version supported?
blender_manifest.tomlwasn't introduced until 4.2.encodingargument forlogging.basicConfigwasn't added until 3.9 (which would make the minimum version Blender 2.93)Note: The build-system version might have to be changed depending on which blender version is targeted. Last version of setuptools with support for 3.8 is
60.2.0