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.

Sign up for GitHub

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

Jump to bottom

The pip_lock rule should fail if either the PY2 or PY3 run fails #34

Open
apt-itude opened this issue Jun 14, 2019 · 0 comments
Open

The pip_lock rule should fail if either the PY2 or PY3 run fails #34

apt-itude opened this issue Jun 14, 2019 · 0 comments
Labels
done Completed in a branch but not yet merged into master
Milestone
v1.0.0

Comments

@apt-itude
Copy link
Owner

Currently, if the PY2 run fails to resolve a dependency, it will proceed to the PY3 run, and the user will most likely miss the failure output and assume it succeeded. It should exit with an error as soon as the first invocation fails.
@apt-itude apt-itude added this to the v1.0.0 milestone Jun 14, 2019
@apt-itude apt-itude added the done Completed in a branch but not yet merged into master label Jul 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
done Completed in a branch but not yet merged into master
Projects
None yet
Milestone
v1.0.0
Development

No branches or pull requests
1 participant
@apt-itude