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
Rename the 'path' argument of the MasterShellCommand 'workdir' #1295
Conversation
I could imagine having a transition period where both are allowed ... I'd rather not ... |
Oh, and saw it ? I'm trying to use git again ! |
LGTM. |
@@ -103,7 +103,7 @@ def test_real_cmd_fails(self): | |||
def test_constr_args(self): | |||
self.setupStep( | |||
master.MasterShellCommand(description='x', descriptionDone='y', | |||
env={'a': 'b'}, path=['/usr/bin'], usePTY=True, | |||
env={'a': 'b'}, workdir=['/usr/bin'], usePTY=True, |
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.
These are definitely wrong - http://twistedmatrix.com/documents/current/api/twisted.internet.interfaces.IReactorProcess.spawnProcess.html says path
is the working directory in which to run the command -- not a list.
Other than the test fixes, yeah -- this just needs docs and a release note. |
I believe this is ok now. |
👍 |
Rename the 'path' argument of the MasterShellCommand 'workdir' - All other steps take a workdir - The path argument is not mentioned in the doc - Even worse, the doc has an example: command="cd dir; do stuff" - As the test show, the one that wrote it believed it would become the PATH.
Few considerations: