Add --no-publish/--no option to spk-convert-pip
#1015
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
This allows the user by pass the "Do you want to also publish these packages? [y/N]: " question, effectively pre-answering it with 'no'. Signed-off-by: David Gilligan-Cook <dcook@imageworks.com>
dcookspi
added
enhancement
rydrman
approved these changes
May 4, 2024
Signed-off-by: David Gilligan-Cook <dcook@imageworks.com>
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
This adds
--no-publish/--nooption to thespk-convert-pipscript. This allows the user to bypass the "Do you want to also publish these packages? [y/N]: " question, effectively pre-answering it with 'no'.The
spk-convert-pipscript already has a--publishoption, which effectively answers 'yes' to the question and goes on to publish the converted packages. But when I was porting python tools from one OS to another, and between one python version and another, I needed a smoother way to convert, but not publish, various versions of python modules. I didn't want to publish each converted version while narrowing down the dependencies for the port, because I knew the latest versions might not play well with other modules. But answering 'no' manually for each conversion was tedious. I added--noto this command to streamline it.