Skip to content
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

Ensure proper execution of subprocesses on MS Windows #22

Open
whart222 opened this issue Jul 6, 2016 · 3 comments
Open

Ensure proper execution of subprocesses on MS Windows #22

whart222 opened this issue Jul 6, 2016 · 3 comments
Milestone

Comments

@whart222
Copy link
Contributor

whart222 commented Jul 6, 2016

The subprocess.run command either does not return the appropriate value or it does not generate output. This branch is focused on resolving this discrepancy.

whart222 added a commit that referenced this issue Jul 6, 2016
But this masks an issue, which is documented in
issue #22.
@ghackebeil
Copy link
Member

What do you mean? We've been using this for quite some time and it seems to work fine.

I'm confused by the commit referenced above as well. The Appveyor tests have been fixed in that failed tests are now reflected in the return code. What was the above commit fixing?

@whart222
Copy link
Contributor Author

whart222 commented Jul 6, 2016

Gabe:

I didn't realize that your commits fixed the return code. But in any case
the output is being masked on MS Windows. So there's still an issue that
needs to be resolved.

--Bill

On Wed, Jul 6, 2016 at 4:48 PM, Gabriel Hackebeil [email protected]
wrote:

What do you mean? We've been using this for quite some time and it seems
to work fine.

I'm confused by the commit referenced above as well. The Appveyor tests
have been fixed in that failed tests are now reflected in the return code.
What was the above commit fixing?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#22 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAsb-NlYQr5LXyXCMCfH6Mvf4x8_yaZnks5qTBSggaJpZM4JGcyV
.

@ghackebeil
Copy link
Member

Agreed. Maybe we should rename this ticket to reflect that. The problem is with output redirection, not the return code.

On Jul 6, 2016, at 4:50 PM, William Hart [email protected] wrote:

Gabe:

I didn't realize that your commits fixed the return code. But in any case
the output is being masked on MS Windows. So there's still an issue that
needs to be resolved.

--Bill

On Wed, Jul 6, 2016 at 4:48 PM, Gabriel Hackebeil [email protected]
wrote:

What do you mean? We've been using this for quite some time and it seems
to work fine.

I'm confused by the commit referenced above as well. The Appveyor tests
have been fixed in that failed tests are now reflected in the return code.
What was the above commit fixing?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#22 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAsb-NlYQr5LXyXCMCfH6Mvf4x8_yaZnks5qTBSggaJpZM4JGcyV
.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@whart222 whart222 changed the title Ensure that return values are preserved in MS Windows Ensure proper execution of subprocesses on MS Windows Jul 6, 2016
@whart222 whart222 added this to the PyUtilib 5.x milestone Oct 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants