Closed rootd00d closed 2 years ago
manylinux2010
wheelsneither of these are a problem with dumb-init
note also that python 3.6 is end-of-lifed so it is not supported either
@asottile Thank you for this excellent feedback!
We're building using container images built upstream, which are all RedHat Enterprise Linux 8.4 and they have explicitly installed Python 3.6. The OS packages are all updated as per our build process, but naturally the python36 package won't magically jump to python38, etc.
While true that these issues are not those of dumb-init -- it's still an issue. Hopefully, we'll be able to get our upstream container images updated to Python(38|39) without breaking literally hundreds of data science projects, but that's seeming like a potentially necessary process.
Cheers!
All of our build pipelines are offline as of the release of the latest PIP version (1.2.5.post1) of the dumb-init package --
Using the previous package works fine --
I'm reaching out in case this package is anomalous -- https://pypi.org/project/dumb-init/#history
Thanks!