-
Notifications
You must be signed in to change notification settings - Fork 251
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
Errors in build.py not logged helpfully in "BUILD FAILED" error message #638
Milestone
Comments
arcivanov
added a commit
to arcivanov/pybuilder
that referenced
this issue
Oct 30, 2019
1. Vendorization of dependencies. 2. New <build-dir>/.pybuilder is created in the project directory to house PyB plugins and plugin dependencies. 3. Dependencies are installed in a venvs with an eye for multi-Python build environments via pyenv 4. New PIP install batching, utilizing pkg_resources and WorkingSet for package inspection. 5. Support for Python 3.7 and 3.8. fixes pybuilder#644, pybuilder#623, pybuilder#607, pybuilder#606, pybuilder#638
arcivanov
added a commit
to arcivanov/pybuilder
that referenced
this issue
Oct 30, 2019
1. Vendorization of dependencies. 2. New <build-dir>/.pybuilder is created in the project directory to house PyB plugins and plugin dependencies. 3. Dependencies are installed in a venvs with an eye for multi-Python build environments via pyenv 4. New PIP install batching, utilizing pkg_resources and WorkingSet for package inspection. 5. Support for Python 3.7 and 3.8. fixes pybuilder#644, pybuilder#623, pybuilder#607, pybuilder#606, pybuilder#638
arcivanov
added a commit
to arcivanov/pybuilder
that referenced
this issue
Oct 30, 2019
1. Vendorization of dependencies. 2. New <build-dir>/.pybuilder is created in the project directory to house PyB plugins and plugin dependencies. 3. Dependencies are installed in a venvs with an eye for multi-Python build environments via pyenv 4. New PIP install batching, utilizing pkg_resources and WorkingSet for package inspection. 5. Support for Python 3.7 and 3.8. fixes pybuilder#644, pybuilder#623, pybuilder#607, pybuilder#606, pybuilder#638
arcivanov
added a commit
to arcivanov/pybuilder
that referenced
this issue
Nov 6, 2019
1. Vendorization of dependencies. 2. New <build-dir>/.pybuilder is created in the project directory to house PyB plugins and plugin dependencies. 3. Dependencies are installed in a venvs with an eye for multi-Python build environments via pyenv 4. New PIP install batching, utilizing pkg_resources and WorkingSet for package inspection. 5. Support for Python 3.7 and 3.8. 6. Coverage accepts module exclusion patterns fixes pybuilder#644, pybuilder#623, pybuilder#607, pybuilder#606, pybuilder#638
Merged
arcivanov
added a commit
to arcivanov/pybuilder
that referenced
this issue
Nov 6, 2019
1. Vendorization of dependencies. 2. New <build-dir>/.pybuilder is created in the project directory to house PyB plugins and plugin dependencies. 3. Dependencies are installed in a venvs with an eye for multi-Python build environments via pyenv 4. New PIP install batching, utilizing pkg_resources and WorkingSet for package inspection. 5. Support for Python 3.7 and 3.8. 6. Coverage accepts module exclusion patterns fixes pybuilder#644, pybuilder#623, pybuilder#607, pybuilder#606, pybuilder#638
arcivanov
added a commit
to arcivanov/pybuilder
that referenced
this issue
Nov 6, 2019
1. Vendorization of dependencies. 2. New <build-dir>/.pybuilder is created in the project directory to house PyB plugins and plugin dependencies. 3. Dependencies are installed in a venvs with an eye for multi-Python build environments via pyenv 4. New PIP install batching, utilizing pkg_resources and WorkingSet for package inspection. 5. Support for Python 3.7 and 3.8. 6. Coverage accepts module exclusion patterns fixes pybuilder#644, pybuilder#623, pybuilder#607, pybuilder#606, pybuilder#638
arcivanov
added a commit
to arcivanov/pybuilder
that referenced
this issue
Apr 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, when there is an error in the
build.py
script itself, the "BUILD FAILED" error message does not provide the full stack trace, nor does the logger provide information about the type of exception or line number. For example:An
AttributeError
example inbuild.py
Given a sample task of:
Where
os.getcwd()
is replaced with the incorrectos.getcd()
, runningpyb
will print the following error message:A more helpful error message would be:
Where
AttributeError
is the type of exception, followed by the message, followed by the line number.An
KeyError
example inbuild.py
Given a task of:
The failure message will be:
A more helpful error message would be:
Where
KeyError
is the type of exception and 22 is the line number.Potential Solution
Using
sys.exc_info()
to capture a tuple containing the exception type and traceback can provide the needed functionality to implement this. A sample implementation in themain
method ofclip.py
might look something like:The text was updated successfully, but these errors were encountered: