Skip to content

pep517.wrappers.BackendUnavailable doesn't actually print out which backend #45

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

Closed
ghost opened this issue Mar 4, 2019 · 3 comments · Fixed by #165
Closed

pep517.wrappers.BackendUnavailable doesn't actually print out which backend #45

ghost opened this issue Mar 4, 2019 · 3 comments · Fixed by #165
Labels

Comments

@ghost
Copy link

ghost commented Mar 4, 2019

I just ran into this error in travis:

E               Traceback (most recent call last):
E                 File "<string>", line 9, in <module>
E                 File "/home/travis/build/kivy/python-for-android/.tox/py3/lib/python3.5/site-packages/pythonforandroid/pythonpackage.py", line 444, in _extract_metainfo_files_from_package_unsafe
E                   reqs = hooks.get_requires_for_build_wheel({})
E                 File "/home/travis/build/kivy/python-for-android/.tox/py3/lib/python3.5/site-packages/pep517/wrappers.py", line 71, in get_requires_for_build_wheel
E                   'config_settings': config_settings
E                 File "/home/travis/build/kivy/python-for-android/.tox/py3/lib/python3.5/site-packages/pep517/wrappers.py", line 162, in _call_hook
E                   raise BackendUnavailable
E               pep517.wrappers.BackendUnavailable

But now I feel left guessing. Which backend? I'm guessing setuptools, but it would be extremely helpful if the error could actually print that out

@pfmoore
Copy link
Member

pfmoore commented Mar 4, 2019

Well, whichever backend your project specifies - but it's a fair point, improving the error would be useful.

@ghost
Copy link
Author

ghost commented Mar 4, 2019

@pfmoore this is called on some random external project indirectly, you've seen my scanning code 🙂 although my own error before could have told me which one and didn't either, so this is as much my own problem 😬 (which I'm already in the process of fixing) but still, would be useful to have more info here

@pradyunsg pradyunsg added the bug label Aug 27, 2020
@pradyunsg
Copy link
Member

Related to #10, but worth keeping open separately.

PRs welcome! ^>^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants