This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
3.0 lib refactor - path tools #697
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
kalisp
reviewed
Nov 11, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Another batch of lib cleanup.
add_tool_to_environment- wasn't used at all -> removedget_ffmpeg_tool_path- moved to path_tools.pyget_last_version_from_path- moved to path_tools.pyget_paths_from_environ- moved to path_tools.pyget_version_from_path- moved to path_tools.pyversion_up- moved to path_tools.py_rreplace- private, moved to path_tools.pygrouper- moved to extract_camera_mayaScene.py, which was the only place of usepairwise- moved to maya.lib. it's is only used by collect_yeti_rig, so it's more appropriatemodified_environ- only usedaportandpremiereProlauncher action, none of which are used anymore - > removed@iLLiCiTiT could you please take those you were asking about in #681 and process them as well? For now I would move the context and database related function to their own module, to at least keep them contained.
BuildWorkfiledeservers it's own home too.