You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
"build":"v40.18.0","support":"","version":40,"description":"SAP BTP Cloud Foundry environment",
cf.exe version 8.7.11+b1b4068ff.2024-07-09
What version of the buildpack you are using?
python_buildpack-cached-cflinuxfs4-v1.8.26.zip
If you were attempting to accomplish a task, what was it you were attempting to do?
I've tried letting cf do pip installation directly, or using vendor for offline deployment.
What did you expect to happen?
I just want to use pandas
What was the actual behavior?
Here is the logs
2024-08-02T14:42:40.24+0800 [STG/0] OUT Using python's pip module
2024-08-02T14:42:41.64+0800 [STG/0] OUT pip 23.0.1 from /tmp/contents2448370566/deps/0/python/lib/python3.10/site-packages/pip (python 3.10)
2024-08-02T14:42:41.69+0800 [STG/0] OUT -----> Running Pip Install (Vendored)
2024-08-02T14:42:42.32+0800 [STG/0] OUT Using the pip --no-build-isolation flag since it is available
ion=w --src=/tmp/contents2448370566/deps/0/src --no-index --find-links=file:///tmp/app/vendor --disable-pip-version-check --n 2024-08-02T14:42:42.81+0800 [STG/0] ERR DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at pypa/pip#11453
2024-08-02T14:42:42.84+0800 [STG/0] OUT Looking in links: file:///tmp/app/vendor, file:///tmp/app/vendor
2024-08-02T14:42:42.85+0800 [STG/0] ERR ERROR: Could not find a version that satisfies the requirement pandas==2.0.3 (from versions: none)
2024-08-02T14:42:42.85+0800 [STG/0] ERR ERROR: No matching distribution found for pandas==2.0.3
2024-08-02T14:42:42.91+0800 [STG/0] OUT Running pip install failed. You need to include all dependencies in the vendor directory.
2024-08-02T14:42:42.91+0800 [STG/0] OUT ERROR Could not install vendored pip packages: could not run pip: exit status 1
2024-08-02T14:42:43.15+0800 [STG/0] ERR Failed to compile droplet: Failed to run all supply scripts: exit status 14
2024-08-02T14:42:43.16+0800 [STG/0] OUT Exit status 223
2024-08-02T14:42:43.46+0800 [STG/0] OUT Cell 1ac9d0b6-79cd-4ce0-8b32-5233625cfca2 stopping instance 990e1653-51b2-405d-b55e-8fd00ce5929a
2024-08-02T14:42:43.46+0800 [STG/0] OUT Cell 1ac9d0b6-79cd-4ce0-8b32-5233625cfca2 destroying container for instance 990e1653-51b2-405d-b55e-8fd00ce5929a
2024-08-02T14:42:43.50+0800 [API/0] ERR Failed to stage build: staging failed
2024-08-02T14:42:45.13+0800 [STG/0] OUT Cell 1ac9d0b6-79cd-4ce0-8b32-5233625cfca2 successfully destroyed container for instance 990e1653-51b2-405d-b55e-8fd00ce5929a
The text was updated successfully, but these errors were encountered:
I think its related to this issue - pypa/setuptools#4519 which requires a newer version of setuptools or to downgrade the version from 72.1. Did you find a way around this issue?
I think its related to this issue - pypa/setuptools#4519 which requires a newer version of setuptools or to downgrade the version from 72.1. Did you find a way around this issue?
Thanks for the reply, I've solved the problem and I managed to solve it after trying a couple of .whl files
Best wishes!!
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
?"build":"v40.18.0","support":"","version":40,"description":"SAP BTP Cloud Foundry environment",
cf.exe version 8.7.11+b1b4068ff.2024-07-09
What version of the buildpack you are using?
python_buildpack-cached-cflinuxfs4-v1.8.26.zip
If you were attempting to accomplish a task, what was it you were attempting to do?
I've tried letting cf do pip installation directly, or using vendor for offline deployment.
What did you expect to happen?
I just want to use pandas
What was the actual behavior?
Here is the logs
2024-08-02T14:42:40.24+0800 [STG/0] OUT Using python's pip module
2024-08-02T14:42:41.64+0800 [STG/0] OUT pip 23.0.1 from /tmp/contents2448370566/deps/0/python/lib/python3.10/site-packages/pip (python 3.10)
2024-08-02T14:42:41.69+0800 [STG/0] OUT -----> Running Pip Install (Vendored)
2024-08-02T14:42:42.32+0800 [STG/0] OUT Using the pip --no-build-isolation flag since it is available
ion=w --src=/tmp/contents2448370566/deps/0/src --no-index --find-links=file:///tmp/app/vendor --disable-pip-version-check --n 2024-08-02T14:42:42.81+0800 [STG/0] ERR DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at pypa/pip#11453
2024-08-02T14:42:42.84+0800 [STG/0] OUT Looking in links: file:///tmp/app/vendor, file:///tmp/app/vendor
2024-08-02T14:42:42.85+0800 [STG/0] ERR ERROR: Could not find a version that satisfies the requirement pandas==2.0.3 (from versions: none)
2024-08-02T14:42:42.85+0800 [STG/0] ERR ERROR: No matching distribution found for pandas==2.0.3
2024-08-02T14:42:42.91+0800 [STG/0] OUT Running pip install failed. You need to include all dependencies in the vendor directory.
2024-08-02T14:42:42.91+0800 [STG/0] OUT ERROR Could not install vendored pip packages: could not run pip: exit status 1
2024-08-02T14:42:43.15+0800 [STG/0] ERR Failed to compile droplet: Failed to run all supply scripts: exit status 14
2024-08-02T14:42:43.16+0800 [STG/0] OUT Exit status 223
2024-08-02T14:42:43.46+0800 [STG/0] OUT Cell 1ac9d0b6-79cd-4ce0-8b32-5233625cfca2 stopping instance 990e1653-51b2-405d-b55e-8fd00ce5929a
2024-08-02T14:42:43.46+0800 [STG/0] OUT Cell 1ac9d0b6-79cd-4ce0-8b32-5233625cfca2 destroying container for instance 990e1653-51b2-405d-b55e-8fd00ce5929a
2024-08-02T14:42:43.50+0800 [API/0] ERR Failed to stage build: staging failed
2024-08-02T14:42:45.13+0800 [STG/0] OUT Cell 1ac9d0b6-79cd-4ce0-8b32-5233625cfca2 successfully destroyed container for instance 990e1653-51b2-405d-b55e-8fd00ce5929a
The text was updated successfully, but these errors were encountered: