Convert Blender-Purge
to a more generic Blender-Crawl
Tool
#42
No reviewers
Labels
No Label
Kind
Breaking
Kind
Bug
Kind: Community
Kind
Documentation
Kind
Easy
Kind
Enhancement
Kind
Feature
Kind
Proposal
Kind
Security
Kind
Studio Request
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/blender-studio-tools#42
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/blender-crawl"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes: studio/blender-studio-pipeline#40
Features
Blender Executable
Directory
Scripts to Execute
Provide Option for "Dry Run"Documentation and Support
Create Basic `Blender-Crawl` scriptto Create `Blender-Crawl` Script for running scripts on mulitple .blend filesCreate `Blender-Crawl` Script for running scripts on mulitple .blend filesto Create `Blender-Crawl` Script for running scripts on many filesCreate `Blender-Crawl` Script for running scripts on many filesto Draft: Create `Blender-Crawl` Script for running scripts on many filesDraft: Create `Blender-Crawl` Script for running scripts on many filesto WIP: Create `Blender-Crawl` Script for running scripts on many filesb4f85c86dd
to04c41fe9df
04c41fe9df
to451fe0c864
@ -0,0 +84,4 @@
return func_wrapper
def cancel_program() -> None:
I don't think there is much of a reason to have this function?
When I look at the code, it seems like all calls to this could be replaced with
sys.exit(0)
without any loss.We handled this together on the phone! Issue has been resolved.
81083cdb01
@ -0,0 +201,4 @@
return path
def setup_config(skip_finding_exec) -> None:
I don't think this program should have any config file at all.
Unless the command line tool is very complex (which this one is not), then the user should always have a fresh start each time the command line tool is run.
I'll elaborate further in an other comment.
We handled this together
9e9c60fda3
issue resolved!@ -0,0 +254,4 @@
# Check config file.
if not config_path.exists() or skip_finding_exec:
print("# Seems like you are starting blender-crawl for the first time!")
While there is a option to skip looking for the blender binary, this is very bad design for a command line tool.
Why? Because this makes it very tedious to script this or run it on multiple computers.
And most importantly, it will stop execution and ask for user input.
For batch scripts this makes it very unreliable because not only does it not do what you wanted to (crawl for blender files), it also stops execution until it has gotten input.
This means that if someone has set this up to run in a bigger script, the script will halt and never finish or give any errors indicating that it didn't execute.
We handled this problem in these commits
9e9c60fda3
76aad47252
489d90b664
to0b7f9b1b1b
WIP: Create `Blender-Crawl` Script for running scripts on many filesto Create `Blender-Crawl` Script for running scripts on many filesCreate `Blender-Crawl` Script for running scripts on many filesto Convert `Blender-Purge` to a more generic `Blender-Crawl` ToolThis should be ready to go now
dba07a1efa
to0087b69e5d
0087b69e5d
to4ec47269d3
4ec47269d3
tod6a332265d