Make the build reproducible

[lamby]

Whilst working on the Reproducible Builds effort we noticed that pydantic could not be built reproducibly. This is due to it generating the contents of the PKG-INFO file via iterating over the contents of a set.

This was originally filed in Debian as #940156.

[codecov]

Codecov Report

Merging #805 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #805   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          17     17           
  Lines        2851   2851           
  Branches      560    560           
=====================================
  Hits         2851   2851

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7704ff8...6499538. Read the comment docs.

[samuelcolvin]

thanks a lot, merged.

Is there somewhere I can check that pydantic is compliant with reproducible-builds.org, or documentation on what you did to build pydantic and notice this?

Or do you just a a script that runs python setup.py build and checks the hash of the artefacts?

[lamby]

Is there somewhere I can check that pydantic is compliant with reproducible-builds.org, or documentation on what you did to build pydantic and notice this?

Sure, I suggest you start here for our automated tests that run against the Debian packages:

https://tests.reproducible-builds.org/debian/pydantic

:)