This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author FFY00
Recipients FFY00, jefferyto, rhettinger, vstinner
Date 2021-05-25.14:35:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I would not expect SOURCE_DATE_EPOCH to sacrifice performance. During packaging, SOURCE_DATE_EPOCH is always set, and sometimes we need to perform expensive operations. We only need this behavior during cache generation, making the solution not optimal.

Backtracking a bit to your proposal for sorting the elements. Is it possible to have two different types with the same name? We need a unique identifier for each type.
After that, we need the type to allow sorting/comparing items, which AFAIK is not something we can guarantee.
We could certainly do the sorting where we are able to, and bail out if impossible, which I feel should handle the majority of cases. This is not optimal, but reasonable.

Is there any way we could something like resetting the hash seed during cache generation?
Date User Action Args
2021-05-25 14:35:13FFY00setrecipients: + FFY00, rhettinger, vstinner, jefferyto
2021-05-25 14:35:13FFY00setmessageid: <>
2021-05-25 14:35:13FFY00linkissue37596 messages
2021-05-25 14:35:13FFY00create