On Fri, 4 Jan 2019 at 16:50, Nick Coghlan firstname.lastname@example.org wrote:
On Thu, 3 Jan 2019 at 11:13, Bert JW Regeer email@example.com wrote:
Is there some way to influence the egg info for the build when using pip wheel? Some thing like:
pip wheel git+https://github.com/org/somerepo.git@ourpatchset#egg=somerepo&egg_info=%2... +local<build number>"
Or is there a better method for dealing with this scenario?
The way auditwheel approaches this is as a "post-process the already built wheel" problem, rather than as a "modify the wheel build process" problem:
- Build the original wheel archive however you'd normally do so
- Unpack the original wheel archive
- Make any desired changes to wheel contents and/or metadata
- Repack the modified wheel (potentially with an updated RECORD file
and modified filename)
auditwheel's own utilities for doing that kind of thing are here: https://github.com/pypa/auditwheel/blob/master/auditwheel/wheeltools.py
It's also worth noting that distlib offers a helper API for modifying wheel archives without needing to write your own archive unpacking and repacking code: https://distlib.readthedocs.io/en/latest/tutorial.html#modifying-wheels