Croniter (for scheduler_events) will be removed on March 15, 2025

pmz · February 21, 2025, 3:11pm

According to the doc:
“A valid cron string that can be parsed by croniter.”

The module page on pypi states that it’s not compliant and will be removed on March 15, 2025.

avc · February 21, 2025, 3:16pm

github.com/frappe/frappe

Croniter may become unlisted

opened 07:46PM - 14 Jan 25 UTC

kehwar

bug

Last December 10, [croniter](https://github.com/corpusops/croniter) published a …[disclaimer](https://github.com/corpusops/croniter/commit/dbeeb1e5ba68a5e1fdee0f03791657e1302d6eea). Among it this stood out to me > I may begin removing any published resources related to this project (e.g., from PyPI, Docker Hub, GitHub, etc.) starting March 15, 2025, especially if the CRA’s risks remain disproportionate. By this I understand that starting March 15 the library may become unlisted and builds of Frappe will fail

github.com/corpusops/croniter

Hopefully not the end

opened 07:19PM - 17 Dec 24 UTC

latk

Earlier today, commit dbeeb1e5ba68a5e1fdee0f03791657e1302d6eea was pushed, which… declared the intention to end development of `croniter` and to maybe unpublish it in the course of 2025. This is due to the maintainers' worries about the EU Cyber Resilience Act, which will enter into force in phases between 2026-06-11 and 2027-12-11. Indeed, the CRA had received massive criticism when initially proposed, though subsequent lobbying by the Open Source community has reduced some of the impact. But as [Felix Reda discusses on the GitHub blog](https://github.blog/open-source/maintainers/what-the-eus-new-software-legislation-means-for-developers/), there are still many question marks about what the CRA will mean in practice, even if it does seem to exempt Open Source projects that aren't developed in the course of a commercial activity. It is completely understandable if you, @kiorky, don't want to bother about any of this. But it would be unnecessarily destructive to unpublish or otherwise remove a package with ~46 million monthly PyPI downloads ([source](https://pypistats.org/packages/croniter)). Please consider an alternative, like passing on control to another maintainer. I am not interested in doing this, but would commit to the bare minimum maintenance if the alternative is that this package enters the eternal /dev/null.