Klipper container missing dependency? about prind HOT 9 CLOSED

Sure, go ahead 🙂

from prind.

Done in Klipper3d/klipper#6550

from prind.

Hey there,
thanks for reaching out.

This seems to be related to upgrading the base images to python 3.12 in #125.
Python 3.12 removed setuptools from the default packages when a venv is created, as described in python/cpython#95299

This should imho be added to the klippy-requirements upstream to achieve compatibility w/ 3.12 and I'll create an PR in the next few days to get this into klipper.

-Markus

from prind.

I can spare some time to submit the PR to Klipper if you don't mind.

from prind.

New PR on Klipper Klipper3d/klipper#6557

from prind.

@mkuf considering how long getting the fix on Klipper is taking, can we add the latest version of python-can as an extra dependency on the container build process and remove when this is fixed upstream?

from prind.

I don't think its a good idea to upgrade a package that klipper depends on here instead of upstream.

As it was stated in your first PR, a viable workaround is to add setuptools without any version pinning to the venv.
I'll prepare a PR to add this to the klipper image.

from prind.

PR has been merged.
setuptools will be included with the next images built by the daily github action run.

I'll leave this issue open for now to observe process in your upstream PRs.

from prind.

In the light of this issue and also #150, I decided that I will revert the klipper base image back to python 3.11, as it does seem that python 3.12 is a bit too bleeding edge for klipper and I favor reliability over up-to-dateness. For now, at least.

-Markus

from prind.