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 georg.brandl
Recipients georg.brandl, josch
Date 2014-10-13.06:57:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
While I can feel your pain regarding the use case you describe, I don't think this has enough general value to add to CPython.  It is not really related to PYTHONHASHSEED, since we never made guarantees about hash values being stable across platforms and Python versions.  PYTHONHASHSEED was introduced to address backwards compatibility for the rare cases where stable hash values are required within a platform/version combination.

Without knowing anything about your libraries, would it not be possible to create a stable representation within the test case for comparison purposes, without having to write the unstable result to a file and then parsing it?  That should be acceptable, given that creating and manipulating those graphs will probably also take significant time in the first place.
Date User Action Args
2014-10-13 06:57:26georg.brandlsetrecipients: + georg.brandl, josch
2014-10-13 06:57:26georg.brandlsetmessageid: <>
2014-10-13 06:57:26georg.brandllinkissue22621 messages
2014-10-13 06:57:26georg.brandlcreate