Files
heroku-buildpack-python/bin/steps
Ed Morley 452443d420 Remove support for the Cedar-14 stack (#1110)
Since the stack is end of life and builds have been disabled:
https://devcenter.heroku.com/changelog-items/1943

There are only two temporarily exempted customers using Python, who
can switch to the Cedar-14 support branch if they still need to build
their Python apps (most of which haven't been built recently).

Closes @W-8054727@.
2020-11-10 13:58:33 +00:00
..
2017-08-28 13:41:32 -04:00
2019-10-09 15:28:31 +02:00
2017-08-03 17:36:23 -04:00
2017-08-03 17:36:23 -04:00
2020-10-07 19:44:33 +01:00
2020-10-07 19:44:33 +01:00
2019-10-09 15:28:31 +02:00
2019-02-21 14:06:20 -08:00
2020-10-06 09:35:36 +01:00

Python Buildpack Install Steps

TODO: Add context on Python install steps, such as why symlinking vs copying

Installing Python packages using Pip

Convention: Use python process to invoke Pip

We don't use this convention (yet) but this is an upcoming change being considered.

This is a bigger concern on Windows than it is in Linux environments, but an emerging convention in the Python community is to invoke pip using:

python3 -m pip [options]

Invoking pip this way ensures correct location - python knows where these packages are stored because it put them there (defaults to Python's pathing info).

All normal command line options are available using this method.