On Thu, Feb 16, 2023 at 6:17 PM Chris Lamb
wrote:
> Thanks. Please feel free to quote my previous email, as well as link
> to my WIP patch.
> Let us know when you have an issue number/URL.
D'oh - unfortunately I only read these after filing the issue, thanks
though. It is reported at:
Hi James,
> I'll file a bug on sphinx's GitHub repository about the original issue
> within the next few hours.
Thanks. Please feel free to quote my previous email, as well as link
to my WIP patch. If you do any of that, I would highly recommend
adding my braindump (starting "Why it hasn't
Hey Chris,
On Wed, Feb 15, 2023 at 7:27 PM Chris Lamb
wrote:
> This change to Sphinx makes alembic reproducible:
>
>
> https://github.com/lamby/sphinx/commit/4ad7670c1df00f82e758aaa8a7b9aaea83b8eaba
>
> Does this patch work for you?
>
Yes! Thank you - that's a much better patch than an
Hey James,
> I noticed what _seemed_ like a quick reproducible-build fix for alembic
> (a database migration framework written in Python). A few hours later
> though, I'm still puzzled.
This seems to be because Sphinx is essentially running repr(…) on a
set() data structure nested within a
Hi folks,
I noticed what _seemed_ like a quick reproducible-build fix for alembic (a
database migration framework written in Python). A few hours later though,
I'm still puzzled.
The problem appears in a similar pattern across various architectures in
the diffoscope results for alembic -- both
