Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add libraries to the python-multi image. #297

Open
chalmerlowe opened this issue Jun 22, 2023 · 0 comments · Fixed by #298
Open

Add libraries to the python-multi image. #297

chalmerlowe opened this issue Jun 22, 2023 · 0 comments · Fixed by #298
Assignees
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@chalmerlowe
Copy link
Contributor

chalmerlowe commented Jun 22, 2023

I often use python-multi to perform troubleshooting on various googleapis libraries.
As part of that troubleshooting, I routinely use the following tools to assist with making edits, running tests (especially nox.sessions), etc.

As such, I typically start my sessions by:

  • installing nox
  • installing vi

Opening this for discussion.
I would like to add both nox and vi to the base build for python-multi.

Will issue a PR related to this shortly.

UPDATE:

In addition, in order to facilitate the install of conda/mamba-based virtual environments, I added conda/mamba to the python-multi Image.

Per request, I added the use of hashed requirements.in/txt files to ensure that exactly the right versions of dependencies were being use.

However... as I began editing the four Dockerfiles for Python-based Docker Images, I noticed that there were several other potential issues/discrepancies that I figured I would ask about:

What is the design principle behind choosing the default version of Python for the various Docker Images:
One has Python 3.6, one has Python 3.8, etc.

@chalmerlowe chalmerlowe added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. priority: p3 Desirable enhancement or fix. May not be included in next release. labels Jun 22, 2023
@chalmerlowe chalmerlowe self-assigned this Jun 22, 2023
@chalmerlowe chalmerlowe reopened this Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant