It seem that they agreed[1] with the solution to transfer the project to the Pallete project[2] (more precisely speaking, its community ecosystem). The Pallet project hosts some popular python libraries such as Flask, werkzeug and jinja which we already heavily depend on. While we can consider replacing croniter where it's not really required, I think we don't have to replace it really urgently at this moment. [1] https://github.com/pallets-eco/croniter/issues/144#issuecomment-2740882901 [2] https://palletsprojects.com/ On 2/11/25 10:35 PM, Thierry Carrez wrote:
Hi everyone,
It was brought to my attention that the croniter maintainer has decided to abandon his project, due to not wanting to deal with his perceived exposure to the EU Cyber-Resilience act (CRA).
https://pypi.org/project/croniter/#disclaimer
The maintainer indicates that you should no longer use it and it may be "unpublished" any time after March 15, 2025. Croniter is being used in at least Mistral, Heat, Watcher, and Aodh as a dependency.
While this is clearly an overreaction (the CRA only applies to "economic operators" putting "products with digital elements" on the market "in the course of a commercial activity"), we should probably prepare to migrate away from this dependency, or maintain a fork of it.