mirror of https://github.com/pulumi/pulumi.git
87b611b1f4
This addresses two issues: 1. `pkg_resource` is deprecated in favor of `importlib.resources` and `importlib.metadata` (https://setuptools.pypa.io/en/latest/pkg_resources.html) 2. Generated provider SDKs don't indicate that they have a dependency on `setuptools` (which includes `pkg_resources`), which can cause problems when installing the package in environments that don't have `setuptools` installed. That's not often common in Pulumi projects, as the virtual environment created by the CLI will include `setuptools`, however, if creating the virtual environment manually with `python -m venv`, `setuptools` is no longer included in the created virtual environment as of Python 3.12. Fixes #12414 Based on #14002, thanks @edgarrmondragon! --------- Co-authored-by: Edgar Ramírez Mondragón <edgarrm358@gmail.com> Co-authored-by: Fraser Waters <fraser@pulumi.com> |
||
|---|---|---|
| .. | ||
| 20230920--programgen--use-importlib-metadata-instead-of-pkg_resources.yaml | ||
| 20231228--backend-filestate--upgrade-gocloud-dev-to-the-latest-version.yaml | ||
| 20240104--auto-go--add-new-api-to-install-the-pulumi-cli-from-the-automation-api.yaml | ||
| 20240122--auto-python--add-new-api-to-install-the-pulumi-cli.yaml | ||
| 20240122--engine--fix-a-hang-in-preview-import-file.yaml | ||
| 20240124--auto-nodejs--allow-disabling-version-validation-when-using-a-custom-pulumicomamnd-instance.yaml | ||
| 20240124--engine--engine-will-now-error-if-aliases-request-a-parent-with-no-urn.yaml | ||
| 20240125--programgen-nodejs--fixes-generated-expression-for-filebase64-function-to-use-fs-readfilesync-directly-with-base64-encoding-option.yaml | ||