Closed fg-j closed 3 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/174628026
The labels on this github issue will be updated when the story is started.
Solved in cf205e2fed0334d7b6b8e6c0118bb7f61c490793. Should be available from next release
Looks like the fix works for my sample app.
After updating the contents of runtime.txt
to contain:
python-3.8.7
I can now cf push
the app and I see the resulting output:
cf push
Pushing from manifest to org system / space my-space as admin...
Using manifest file /home/ubuntu/workspace/cloudfoundry/python-buildpack/sample-app/manifest.yml
Getting app info...
...
...
...
Downloaded app package (7.4K)
-----> Python Buildpack version 1.7.28.20210107191246
-----> Supplying Python
-----> Installing python 3.8.7
Download [https://buildpacks.cloudfoundry.org/dependencies/python/python_3.8.7_linux_x64_cflinuxfs3_4abd87d1.tgz]
-----> Installing pip-pop 0.1.5
Download [https://buildpacks.cloudfoundry.org/dependencies/manual-binaries/pip-pop/pip-pop-0.1.5-b32efe86.tar.gz]
Generating 'requirements.txt' from Pipfile.lock
-----> Running Pip Install
Looking in indexes: https://pypi.org/simple, https://test.pypi.org/simple
So it does seem like the change makes Pip able to see both desired indexes.
What version of the buildpack you are using? Multiple versions including
1.7.20
If you were attempting to accomplish a task, what was it you were attempting to do?
cf push
this sample appWhat did you expect to happen? The buildpack should generate a
requirements.txt
file during the build that uses the--extra-index-url
flag, since there are multiple sources in thePipfile.lock
What was the actual behavior? The buildpack generates a
requirements.txt
file that looks like:Note that includes two instances of the
-i
flag, wherepip install
will only accept one. (See this post) and thepip man
page linked therein.The faulty line of code within the buildpack is here.
Please confirm where necessary: