-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kp pytools to warptools pd 2186 #1026
base: develop
Are you sure you want to change the base?
Conversation
Remember to squash merge! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @kevinpalis, would you mind making a couple of doc updates to go along with these changes? If you have any questions please let me know. Thanks so much!
Remember to squash merge! |
Remember to squash merge! |
Remember to squash merge! |
Remember to squash merge! |
@kevinpalis Thanks for making those doc updates! |
Remember to squash merge! |
Remember to squash merge! |
Remember to squash merge! |
Remember to squash merge! |
Remember to squash merge! |
Remember to squash merge! |
…ries that just won't work with a more recent python container
Remember to squash merge! |
We have already moved the custom python scripts and the docker file for the pytools image into warp-tools. We do not want to have duplicate code.
This PR will remove all usage of pytools in WARP and replace them with the latest warp-tools image that is semantically versioned (ie. not a test container). This also changes the path of the scripts in the container so a minor change to command calls is necessary.
Checklist
If you can answer "yes" to the following items, please add a checkmark next to the appropriate checklist item(s) and notify our WARP documentation team by tagging either @ekiernan or @kayleemathews in a comment on this PR.