Set Executable File #71
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds the ability to use a custom
rcloneexecutable path instead of relying solely on the systemPATH.Changes
New
set_executable_file()Functionrcloneexecutablevalidateparameter (default:True) to verify the executable path existsFileNotFoundErrorif the path does not exist and validation is enabledvalidate=Falsefor advanced use casesUpdated
is_installed()rclonewas available in the systemPATHTrueif a valid custom executable path has been configured viaset_executable_file()@__check_installedwork correctly when using a custom executableTests Added
test_set_executable_file()Verifies that the custom executable path is correctly stored
test_default_executable_path()Confirms the default executable is
"rclone"test_set_executable_file_validation()Tests executable path validation behavior
test_is_installed_with_custom_executable()Ensures
is_installed()works correctly with a custom executable pathtest_executable_used_in_command()Confirms that the custom executable is actually used when running
rclonecommands