-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
After many refactoring/preparation PRs, we're now ready to add support for the package manager Poetry: https://python-poetry.org To use Poetry, apps must have a `poetry.lock` lockfile, which can be created by running `poetry lock` locally, after adding Poetry config to `pyproject.toml` (which can be done either manually or by using `poetry init`). For now, if a `requirements.txt` or `Pipfile` is found it will take precedence over `poetry.lock` for backwards compatibility (in the future this will become a warning then an error). This means users of the third-party `python-poetry-buildpack` will need to remove that buildpack in order to use the new native Poetry support, since it exports a `requirements.txt` file during the build. Poetry is installed into the build cache rather than the slug, so is not available at run-time (since it's not typically needed at run-time and doing so reduces the slug size). The entrypoints of installed dependencies are available on `PATH`, so use of `poetry run` or `poetry shell` is not required at run-time to use dependencies in the environment. When using Poetry, pip is not installed since Poetry includes its own internal vendored copy that it will use instead (for the small number of Poetry operations for which it still calls out to pip, such as package uninstalls). During normal (non-CI) builds, the `poetry install --sync` command is run using `--only main` so as to only install the main `[tool.poetry.dependencies]` dependencies group from `pyproject.toml` and not any of the app's other dependency groups (such as test/dev/... groups, eg `[tool.poetry.group.test.dependencies]`). On Heroku CI, all default Poetry dependency groups are installed (i.e. all groups minus those marked as `optional = true`). Relevant Poetry docs: - https://python-poetry.org/docs/cli/#install - https://python-poetry.org/docs/configuration/ - https://python-poetry.org/docs/managing-dependencies/#dependency-groups See also the Python CNB equivalent of this PR: - heroku/buildpacks-python#261 Note: We don't support controlling the Python version via Poetry's `tool.poetry.dependencies.python` field, since that field typically contains a version range, which is not safe to use. Use the newly added `.python-version` file support instead. For more on this, see the longer explanation over in the Python CNB repo: heroku/buildpacks-python#260 Closes #796. Closes #835. GUS-W-16810914.
- Loading branch information
Showing
48 changed files
with
954 additions
and
22 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,133 @@ | ||
#!/usr/bin/env bash | ||
|
||
# This is technically redundant, since all consumers of this lib will have enabled these, | ||
# however, it helps Shellcheck realise the options under which these functions will run. | ||
set -euo pipefail | ||
|
||
POETRY_VERSION=$(utils::get_requirement_version 'poetry') | ||
|
||
function poetry::install_poetry() { | ||
local python_home="${1}" | ||
local cache_dir="${2}" | ||
local export_file="${3}" | ||
|
||
# We store Poetry in the build cache, since we only need it during the build. | ||
local poetry_root="${cache_dir}/.heroku/python-poetry" | ||
|
||
# We nest the venv and then symlink the `poetry` script to prevent the rest of `venv/bin/` | ||
# (such as entrypoint scripts from Poetry's dependencies, or the venv's activation scripts) | ||
# from being added to PATH and exposed to the app. | ||
local poetry_bin_dir="${poetry_root}/bin" | ||
local poetry_venv_dir="${poetry_root}/venv" | ||
|
||
meta_set "poetry_version" "${POETRY_VERSION}" | ||
|
||
# The earlier buildpack cache invalidation step will have already handled the case where the | ||
# Poetry version has changed, so here we only need to check that a valid Poetry install exists. | ||
# venvs are not relocatable, so if the cache directory were ever to change location, the cached | ||
# Poetry installation would stop working. To save having to track the cache location via build | ||
# metadata, we instead rely on the fact that relocating the venv would also break the absolute | ||
# path `poetry` symlink created below, and that the `-e` condition not only checks that the | ||
# `poetry` symlink exists, but that its target is also valid. | ||
# Note: Whilst the Codon cache location remains stable from build to build, for Heroku CI the | ||
# cache directory currently does not, so the cached Poetry will always be invalidated there. | ||
if [[ -e "${poetry_bin_dir}/poetry" ]]; then | ||
output::step "Using cached Poetry ${POETRY_VERSION}" | ||
else | ||
output::step "Installing Poetry ${POETRY_VERSION}" | ||
|
||
# The Poetry directory will already exist in the relocated cache case mentioned above. | ||
rm -rf "${poetry_root}" | ||
|
||
python -m venv --without-pip "${poetry_venv_dir}" | ||
|
||
# We use the pip wheel bundled within Python's standard library to install Poetry. | ||
# Whilst Poetry does still require pip for some tasks (such as package uninstalls), | ||
# it bundles its own copy for use as a fallback. As such we don't need to install pip | ||
# into the Poetry venv (and in fact, Poetry wouldn't use this install anyway, since | ||
# it only finds an external pip if it exists in the target venv). | ||
local bundled_pip_module_path | ||
bundled_pip_module_path="$(utils::bundled_pip_module_path "${python_home}")" | ||
|
||
if ! { | ||
python "${bundled_pip_module_path}" \ | ||
--python "${poetry_venv_dir}" \ | ||
install \ | ||
--disable-pip-version-check \ | ||
--no-cache-dir \ | ||
--no-input \ | ||
--quiet \ | ||
"poetry==${POETRY_VERSION}" | ||
}; then | ||
output::error <<-EOF | ||
Error: Unable to install Poetry. | ||
Try building again to see if the error resolves itself. | ||
If that does not help, check the status of PyPI (the Python | ||
package repository service), here: | ||
https://status.python.org | ||
EOF | ||
meta_set "failure_reason" "install-poetry" | ||
return 1 | ||
fi | ||
|
||
mkdir -p "${poetry_bin_dir}" | ||
# NB: This symlink must not use `--relative`, since we want the symlink to break if the cache | ||
# (and thus venv) were ever relocated - so that it triggers a reinstall (see above). | ||
ln --symbolic --no-target-directory "${poetry_venv_dir}/bin/poetry" "${poetry_bin_dir}/poetry" | ||
fi | ||
|
||
export PATH="${poetry_bin_dir}:${PATH}" | ||
echo "export PATH=\"${poetry_bin_dir}:\${PATH}\"" >>"${export_file}" | ||
# Force Poetry to manage the system Python site-packages instead of using venvs. | ||
export POETRY_VIRTUALENVS_CREATE="false" | ||
echo 'export POETRY_VIRTUALENVS_CREATE="false"' >>"${export_file}" | ||
} | ||
|
||
# Note: We cache site-packages since: | ||
# - It results in faster builds than only caching Poetry's download/wheel cache. | ||
# - It's safe to do so, since `poetry install --sync` fully manages the environment | ||
# (including e.g. uninstalling packages when they are removed from the lockfile). | ||
# | ||
# With site-packages cached there is no need to persist Poetry's download/wheel cache in the build | ||
# cache, so we let Poetry write it to the home directory where it will be discarded at the end of | ||
# the build. We don't use `--no-cache` since the cache still offers benefits (such as avoiding | ||
# repeat downloads of PEP-517/518 build requirements). | ||
function poetry::install_dependencies() { | ||
local poetry_install_command=( | ||
poetry | ||
install | ||
--sync | ||
) | ||
|
||
# On Heroku CI, all default Poetry dependency groups are installed (i.e. all groups minus those | ||
# marked as `optional = true`). Otherwise, only the 'main' Poetry dependency group is installed. | ||
if [[ ! -v INSTALL_TEST ]]; then | ||
poetry_install_command+=(--only main) | ||
fi | ||
|
||
# We only display the most relevant command args here, to improve the signal to noise ratio. | ||
output::step "Installing dependencies using '${poetry_install_command[*]}'" | ||
|
||
# `--compile`: Compiles Python bytecode, to improve app boot times (pip does this by default). | ||
# `--no-ansi`: Whilst we'd prefer to enable colour if possible, Poetry also emits ANSI escape | ||
# codes for redrawing lines, which renders badly in persisted build logs. | ||
# shellcheck disable=SC2310 # This function is invoked in an 'if' condition so set -e will be disabled. | ||
if ! { | ||
"${poetry_install_command[@]}" --compile --no-ansi --no-interaction \ | ||
|& tee "${WARNINGS_LOG:?}" \ | ||
|& grep --invert-match 'Skipping virtualenv creation' \ | ||
|& output::indent | ||
}; then | ||
show-warnings | ||
|
||
output::error <<-EOF | ||
Error: Unable to install dependencies using Poetry. | ||
See the log output above for more information. | ||
EOF | ||
meta_set "failure_reason" "install-dependencies::poetry" | ||
return 1 | ||
fi | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
poetry==1.8.4 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
3.12 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
{ | ||
"environments": { | ||
"test": { | ||
"scripts": { | ||
"test": "./bin/print-env-vars.sh && pytest --version" | ||
} | ||
} | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
#!/usr/bin/env bash | ||
|
||
# This file is run by the inline buildpack, and tests that the environment is | ||
# configured as expected for buildpacks that run after the Python buildpack. | ||
|
||
set -euo pipefail | ||
|
||
BUILD_DIR="${1}" | ||
|
||
cd "${BUILD_DIR}" | ||
|
||
exec bin/print-env-vars.sh |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
#!/usr/bin/env bash | ||
|
||
# This file is run by the inline buildpack. | ||
|
||
set -euo pipefail | ||
|
||
echo "Inline" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
#!/usr/bin/env bash | ||
|
||
set -euo pipefail | ||
|
||
exec bin/print-env-vars.sh |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
#!/usr/bin/env bash | ||
|
||
set -euo pipefail | ||
|
||
printenv | sort | grep -vE '^(_|BUILDPACK_LOG_FILE|BUILD_DIR|CACHE_DIR|CI_NODE_.+|DYNO|ENV_DIR|HEROKU_TEST_RUN_.+|HOME|OLDPWD|PORT|PWD|SHLVL|STACK|TERM)=' |
Oops, something went wrong.