Closed fmoessbauer closed 2 years ago
I'm not sure you're meant to compare setup.cfg
byte-for-byte.
If you need to programmatically check consistency, you could parse the files (into dicts/objects) first. afaik the PyPI file is generated by python setup.py sdist
^1 and therefore has different whitespaces plus also an extra block:
[egg_info]
tag_build =
tag_date = 0
Ok, thanks for the clarification. Then I'll simply use the archive from PyPI.
Hi,
I'm working on packaging shtab for Debian and while doing so I discovered a reproducability glitch: The
setup.cfg
in the git repository useskey=value
, while thesetup.cfg
in the archive from PyPI useskey = value
syntax (note the spaces).This is problematic as we assume that the sources archive distributed via PyPI is identical with the upstream repository.