Skip to content
This repository has been archived by the owner on Jan 15, 2023. It is now read-only.

Use pipx for all global python binaries #297

Merged
merged 2 commits into from
Jul 20, 2020
Merged

Use pipx for all global python binaries #297

merged 2 commits into from
Jul 20, 2020

Conversation

mhart
Copy link
Member

@mhart mhart commented Jul 20, 2020

- Add /root/.local/bin to PATH
- Add pipx to base build images
- Update aws-lambda-builders to 1.0.0
- Update dotnetcore3.1 build SDK to 3.1.302
@mhart
Copy link
Member Author

mhart commented Jul 20, 2020

In case this breaks anyone's workflow, all existing build images have been tagged and published as:

lambci/lambda:20200719-build-${RUNTIME}

(eg, lambci/lambda:20200719-build-python3.6)

@mhart mhart merged commit ed7e7e9 into master Jul 20, 2020
@jfuss
Copy link
Contributor

jfuss commented Jul 20, 2020

@mhart Thanks for doing this. This looks good from what I can tell. I would have just used venv directly but pipx works too. Does pipx put the clis into the path automatically?

@mhart
Copy link
Member Author

mhart commented Jul 20, 2020

Yeah it does – saves a bit of fiddling that would come with manually doing this from venvs

@twasink
Copy link

twasink commented Jul 21, 2020

From what I can tell from the docs, if you set the PIPX_BIN_DIR variable as part of doing the various pipx install steps, you could install the binaries into a path that wasn't in the /root/ dir, and thus into a place readable by non-root users - e.g. /usr/local/bin or /opt/bin.

This would avoid the whole "breaking people's workflow" problem.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants