Closed jayaddison closed 8 months ago
I'm guessing a release to pypi would be appreciated once this is merged, right?
is it being consumed from teh release? our own reqs likely point to the github
don't know but I think debian would likely prefer to package a tag / release instead of the main branch
I'm guessing a release to pypi would be appreciated once this is merged, right?
Probably, yep - I think it's feasible to package an update without them, but in terms of having more easily comprehensible/comparable package versions, yep, that'd be helpful for Debian.
(also: thank you for the code review)
Ek, I forgot the space before the %Z
. One moment..
let's try it out
ok that's released, 1.5.0 (though SQLAlchemy's own doc reqs point to the github)
It's looking good to me so far, thanks again both. An automated reproducibility test of mako
with zzzeeksphinx
v1.5.0 produces a successful result with this change in place. I'll continue to check on that and sqlalchemy
documentation builds over the next few weeks.
This updates the base theme layout to respect the
SOURCE_DATE_EPOCH
reproducible build environment variable when it is present, improving support for reproducible documentation builds.Appearance / text format:
Source-date-epoch timestamp
Local system timestamp
Resolves #23.