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 martin.panter
Recipients martin.panter, ned.deily, ronaldoussoren, serhiy.storchaka, vstinner
Date 2020-01-25.05:09:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Of course I would prefer “crc_hqx” to stay, because we use it at work. But I understand if you think it is not popular enough to justify maintaining it.

But I was more asking if the deprecation notice should point the way forward. This function is no longer recommended, so what should users do instead? Or at least explain why it is deprecated.

In my case, I may eventually write or resurrect a simple Python CRC implementation that shifts one bit at a time. But other people may desire a faster C implementation.
Date User Action Args
2020-01-25 05:09:55martin.pantersetrecipients: + martin.panter, ronaldoussoren, vstinner, ned.deily, serhiy.storchaka
2020-01-25 05:09:55martin.pantersetmessageid: <>
2020-01-25 05:09:55martin.panterlinkissue39353 messages
2020-01-25 05:09:55martin.pantercreate