Closed blimmer closed 2 years ago
Hi @blimmer - thanks for bringing this up.
pipenv --rm
then pipenv install
resets the cache and builds with the correct version
the way pipenv looks and uses python is to use the highest version here
best practice would be to specify which version of python to use e.g pipenv install --python=3.9.15
, but i agree it should match the tag. if anyone wants to change the version, they can always specify
@JalexChen - thank you! It looks like this change wasn't published to DockerHub. What're your thoughts about releasing this?
Hey @blimmer - general policy is to only respin if there are security issues. Since there is a wrokaround, these changes will be reflected for the next release.
I use
pipenv
to manage dependencies for a project. With the new version ofcimg/python:3.9.15
(sha256:b74e50b094007f94d474df2707b6ce60b7c438eabfce64561a4305ee4a6a72d7
),pipenv
uses version3.10.6
of Python (vs. the expected3.9.15
version).The key from these logs is:
Which is unexpected.
This did not occur with the
cimg/python:3.9.14
image:It used the correct version for the
pipenv
:But,
/usr/bin/python3
is oddly 3.8.10 on this image, as well...In my opinion, every possible incantation of running
python
in thecimg/python
images should always use the version specified in the tag.