-
Notifications
You must be signed in to change notification settings - Fork 49
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
AttributeError: 'Pep517HookCaller' object has no attribute 'build_sys_requires' #14
Comments
This issue also happens when attempting to use |
Looks like a straight bug. I've no idea what |
I added the following diff and it bypasses the error: diff --git a/pep517/wrappers.py b/pep517/wrappers.py
index b14b899..62051dc 100644
--- a/pep517/wrappers.py
+++ b/pep517/wrappers.py
@@ -43,6 +43,8 @@ class Pep517HookCaller(object):
source_dir : The path to the source directory, containing pyproject.toml.
backend : The build backend spec, as per PEP 517, from pyproject.toml.
"""
+ build_sys_requires = []
+
def __init__(self, source_dir, build_backend):
self.source_dir = abspath(source_dir)
self.build_backend = build_backend Actually, I'm not confident in that statement... |
That seems like the wrong approach to me - it's just patching over the real problem here, which is that The lack of actual documentation is the fundamental problem here, compounded by the As I said elsewhere, anything other than the |
My understanding was that |
After applying that patch,
|
Installing flit allows the check to run:
|
I'll leave that to @takluyver to comment on. I don't think it is, or should be, but this isn't technically my project, so I'm not really in a position to make that call. When I've pointed people to this project, it's been solely for the |
#23 should fix it.
It checks that a package can be built using the PEP 517 interface. You run It's not intended as a way of getting the distributions - it builds them in a tempdir which is deleted when it finished. |
(For reference, if you actually want the distributions, the highest level API is |
@takluyver thanks for spotting the issue - as you say, it was missed when I refactored the hook callers for pip. Your explanation of |
To reproduce:
I believe
check_build_wheel
also contains this non-existent attribute reference.The text was updated successfully, but these errors were encountered: