-
Notifications
You must be signed in to change notification settings - Fork 99
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
setup.py still ok? #194
Comments
@jafingerhut there is a PR open to address this: #193 The issue is caused by this line: Line 25 in bb28a88
While the syntax is correct, support for the file: attribute in install_requires was added recently to setuptools. It requires a toolchain more recent than what you'd get by default in Ubuntu 20.04 or even Ubuntu 22.04.
I am waiting for the contributor to address my comment about updating the README before merging the PR. I would still recommend using ptf/.github/workflows/build.yml Lines 36 to 39 in bb28a88
|
Lots of more details here: https://docs.google.com/spreadsheets/d/12qip0oKFVK1vPXdC7-VtnRYit-BxKdfsZJPJrDB_usI/edit?usp=sharing As of the 2023-Jun-19 version of this ptf repo, |
@jafingerhut your doc is not public We are still waiting on #197 in order to fix this issue |
Sorry about that. Should be public to anyone with the link now, and I've updated the link in the comment above in case it changed as a result. |
Before this commit: ff79b8c
I had a bash script that was installing ptf this way on an Ubuntu 20.04 system:
After that commit, there is an exception thrown when I attempt that
setup.py install
command.Should that command still work?
Is it anti-recommended to install ptf that way from source code?
Perhaps I should be using
sudo pip install .
instead?The text was updated successfully, but these errors were encountered: