What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running cf curl /v2/info && cf version?
cf version 6.47.1+0921a21b7.2019-10-18
What version of the buildpack you are using?
https://github.com/cloudfoundry/python-buildpack
v1.7.1
If you were attempting to accomplish a task, what was it you were attempting to do?
Installling vendored dependencies
What did you expect to happen?
Successfully install all vendored dependencies
What was the actual behavior?
Erorr during installing vendored dependencies:
-----> Python Buildpack version 1.7.1
-----> Supplying Python
-----> Installing python 3.8.0
Copy [/tmp/cache/final/dependencies/cabbf104215db0e7ded4b2d65b3de8abfed4bb146a4cd61eacda7dbcc561925a/python-3.8.0-linux-x64-cflinuxfs3-6af4e503.tgz]
-----> Installing pip-pop 0.1.3
Copy [/tmp/cache/final/dependencies/3b86fb2cd9c13268f8858fd0ccb2f9eaf11295a51804b7075fe38d7e2a471191/pip-pop-0.1.4-0a3b0f1b.tar.gz]
Generating 'requirements.txt' from Pipfile.lock
-----> Running Pip Install
Using the pip --no-build-isolation flag since it is available
Looking in links: file:///tmp/app/vendor
Collecting attrs==19.3.0 (from -r /tmp/app/requirements.txt (line 2))
Preparing wheel metadata: started
Preparing wheel metadata: finished with status 'error'
ERROR: Command errored out with exit status 1:
command: /tmp/contents687858878/deps/0/bin/python /tmp/contents687858878/deps/0/python/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /tmp/tmp_h2bnk_n
cwd: /tmp/pip-install-d90u0avf/attrs
Complete output (14 lines):
running dist_info
creating /tmp/pip-install-d90u0avf/attrs/pip-wheel-metadata/attrs.egg-info
writing /tmp/pip-install-d90u0avf/attrs/pip-wheel-metadata/attrs.egg-info/PKG-INFO
writing dependency_links to /tmp/pip-install-d90u0avf/attrs/pip-wheel-metadata/attrs.egg-info/dependency_links.txt
writing requirements to /tmp/pip-install-d90u0avf/attrs/pip-wheel-metadata/attrs.egg-info/requires.txt
writing top-level names to /tmp/pip-install-d90u0avf/attrs/pip-wheel-metadata/attrs.egg-info/top_level.txt
writing manifest file '/tmp/pip-install-d90u0avf/attrs/pip-wheel-metadata/attrs.egg-info/SOURCES.txt'
reading manifest file '/tmp/pip-install-d90u0avf/attrs/pip-wheel-metadata/attrs.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
no previously-included directories found matching 'docs/_build'
warning: no previously-included files found matching 'changelog.d/*.rst'
writing manifest file '/tmp/pip-install-d90u0avf/attrs/pip-wheel-metadata/attrs.egg-info/SOURCES.txt'
creating '/tmp/pip-install-d90u0avf/attrs/pip-wheel-metadata/attrs.dist-info'
error: invalid command 'bdist_wheel'
----------------------------------------
ERROR: Command errored out with exit status 1: /tmp/contents687858878/deps/0/bin/python /tmp/contents687858878/deps/0/python/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /tmp/tmp_h2bnk_n Check the logs for full command output.
Running pip install without indexes failed. Not all dependencies were vendored. Trying again with indexes.
Collecting attrs==19.3.0 (from -r /tmp/app/requirements.txt (line 9))
Downloading https://files.pythonhosted.org/packages/a2/db/4313ab3be961f7a763066401fb77f7748373b6094076ae2bda2806988af6/attrs-19.3.0-py2.py3-none-any.whl
So the build first tries to install from file:///tmp/app/vendor after one dependency fails, it reads the requirements.txt and download the package, which then works correctly...
I think it's an error according the pip version:
WARNING: You are using pip version 19.2.3, however version 19.3.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
On my local machine with pip version 19.3.1 it works, when I run pip download -r requirements.txt --no-binary=:all: -d vendor. However it failed when I downgrade to the same version as in the buildpack (19.2.3). Even after I updated wheel to 0.33.6 and setuptools to 41.6.0 (was 41.2.0 before).
So the error could be solved if we try to upgrade pip to the newest version. However I don't know if the process with pip download -r requirements.txt --no-binary=:all: -d vendor is the same as the process the python buildpack does, when installing from vendor directory
Please confirm where necessary:
What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running
cf curl /v2/info && cf version?cf version 6.47.1+0921a21b7.2019-10-18
What version of the buildpack you are using?
https://github.com/cloudfoundry/python-buildpack
v1.7.1
If you were attempting to accomplish a task, what was it you were attempting to do?
Installling vendored dependencies
What did you expect to happen?
Successfully install all vendored dependencies
What was the actual behavior?
Erorr during installing vendored dependencies:
So the build first tries to install from
file:///tmp/app/vendorafter one dependency fails, it reads therequirements.txtand download the package, which then works correctly...I think it's an error according the
pipversion:On my local machine with pip version 19.3.1 it works, when I run
pip download -r requirements.txt --no-binary=:all: -d vendor. However it failed when I downgrade to the same version as in the buildpack (19.2.3). Even after I updatedwheelto 0.33.6 andsetuptoolsto 41.6.0 (was 41.2.0 before).So the error could be solved if we try to upgrade
pipto the newest version. However I don't know if the process withpip download -r requirements.txt --no-binary=:all: -d vendoris the same as the process the python buildpack does, when installing from vendor directoryPlease confirm where necessary: