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

Don't ignore exit codes when using setuptools entry points #280

Merged
merged 3 commits into from
Jul 7, 2016
Merged

Don't ignore exit codes when using setuptools entry points #280

merged 3 commits into from
Jul 7, 2016

Commits on Jul 6, 2016

  1. Failing test for pex-tool#137

    @rouge8
    rouge8 committed Jul 6, 2016
    Configuration menu
    Copy the full SHA
    f8b14d0 View commit details
    Browse the repository at this point in the history

  2. Don't ignore exit codes when using setuptools entry points 

    Setuptools does not require `console_scripts` entry points to call
`sys.exit()` (or similar) to exit non-zero:

    The functions you specify are called with no arguments, and their
    return value is passed to `sys.exit()`, so you can return an
    errorlevel or message to print to stderr

This patch updates pex to follow the same behavior.

Fixes pex-tool#137.
    @rouge8
    rouge8 committed Jul 6, 2016
    Configuration menu
    Copy the full SHA
    4134578 View commit details
    Browse the repository at this point in the history

Commits on Jul 7, 2016

  1. Exit from PEX.execute_script()

    @rouge8
    rouge8 committed Jul 7, 2016
    Configuration menu
    Copy the full SHA
    9fb1666 View commit details
    Browse the repository at this point in the history