Generate Python egg-info from automake builds (4.18.x) #2341
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To compensate for the loss of egg-info from the python distutils build, create one ourselves. This is effectively a backport of e31fb5b which dismissed the need for an automake version, but unfortunately Python 3.12 and automake-based rpm versions do co-exist in the same time-space continuum and we'll have to deal with this in rpm 4.18 as well. As to why not just use distutils from python-setuptools: that variant turns the egg-info into a directory, which in rpm is a one-way street. And we don't need that multi megabyte Python library to fill in these couple of values, really.
pmatilai
changed the title
|
My sentiments exactly... |
|
Just noting that this will need a mention in the release notes when the time comes: the setup.py build is not compatible with Python >= 3.12 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To compensate for the loss of egg-info from the python distutils build, create one ourselves.
This is effectively a backport of e31fb5b which dismissed the need for an automake version, but unfortunately Python 3.12 and automake-based rpm versions do co-exist in the same time-space continuum and we'll have to deal with this in rpm 4.18 as well.
As to why not just use distutils from python-setuptools: that variant turns the egg-info into a directory, which in rpm is a one-way street. And we don't need that multi megabyte Python library to fill in these couple of values, really.