- Brendan-Parmer changed review status to Awaiting Review
- 1 mo
This extension requests the following permission:
Creates and writes to files in a specified directory
Hi there! I've tested in Composition Nodes (Create Script). I've pasted the clipboard to NotePad++ and adapted the code to my needs. Installs fails with this error:
"inconsistent use of tabs and spaces in indentation (init.py, line xxxx)"
After replacing that bad tabs, the source works perfectly.
I didn't see a .blend1
file in the original v3.2.0 zip, but there were some pycache/
directories that needed cleaned up. I've also made a couple bug fixes for v3.2.1
Why does this have 4.3 as the maximum version? Maximum version means add-on is not supported from that version forward, meaning this will only for 4.2. Is that intended?
Hi @OlyDJ, NodeToPython currently defaults to using tabs for its generated indentation, but I like the idea of supporting both spaces and tabs. I've created a feature request on GitHub where you can track the progreses
Hi @nickberckley, yes it was intentional to set Blender 4.3 as the max version for NTPv3.2.
Aside from not supporting new nodes or node features very well, NodeToPython usually breaks on new minor releases. It's usually smaller things like dealing with newly-deprecated node attributes, but sometimes there's more serious breaking API changes that need attention.
Mostly, I don't want to give users the impression that new Blender versions are officially supported before I've had a chance to update the addon. I'm happy to remove the max version from the manifest if this isn't the proper usage of it, though.
Hey everyone,
Just a heads-up about a recent change regarding the licensing of add-ons on the Blender extension platform. Moving forward, all add-ons will need to be released under the GNU/GPL 3.0 license (SPDX:GPL-3.0-or-later). This is mainly to keep things simple and consistent across the board.
Previously, we accepted various licenses as long as they were compatible with Blender’s distribution. However, to avoid any confusion and streamline the process, all add-ons using the bpy API should now be presented as GPL 3 (the same license the Blender bundle is distributed). Regardless of whether the original code was under GPL 2, or something else like MIT or ZLIB.
Existing add-ons versions won't be affected. However, new updates will need to comply to the revised requirements.
Thanks for understanding, and feel free to reach out if you have any questions.
Alright makes sense. I'll approve this with the expectation that license will be updated afterwards.
Sign in to comment.
Ready for review