gtristan commented on PR #1837: URL: https://github.com/apache/buildstream/pull/1837#issuecomment-1514157075
> > As I understand it, Python 3.8 can be installed on RHEL/CentOS 7 using `rh-python38` from Red Hat Software Collections 3.8. > > Trying to verify this, "Red Hat Software Collections 3.8" doesn't appear to be something accessible for Centos 7, for centos there appears to be "The Software Collections ( SCL ) Repository" installable with yum, but despite rumors on the internets indicating that this would contain `rh-python38`, it does not appear to be the case as far as I can see. > > I'll keep spelunking for a bit, and will likely just resort to using a BuildStream 2.x which supports python 3.6 since this appears to be the path of least resistance, in this case I'll try to make sure the magic wheel also gets built, use that directly, and we can discuss separately whether or not to merge this. Conclusion here is that it is not installable from `centos-sclo-rh`, even if all evidence to the contrary exists on the internets. The issue here probably is that it would require a `yum update` to refresh everything and get access to new packages which include the `rh-python38-python` package, which I'm not yet certain would be acceptable to do in this specific centos7 based build container image. I may resort to building/installing python 3.8 from source here as a less disruptive option. > > Also, I expect that Python 3.6 support would cause issues over time, if not already. Python libraries tend to drop support for obsolete Python versions, which make the latest versions uninstallable. I.e., I'd prefer not merging this, if we can avoid it. > > I think you're talking specifically about the frozen set of dependencies we use for testing. > It looks like it's even worse than I expected... attempting to get buildstream to build/install on python 3.6 requires additional reverts in buildstream, and I've encountered some errors (indirect dependency of ujson -> setuptools_scm) which don't seem feasible to work around, at least not with an automated `pip install`. Likelyhood of dropping this PR altogether is raised exponentially ;-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
