Split the python version and the rust version into two separate projects.

[ghost]

Could $SUBJ be implemented, please?

The difference between version 2.1 and 3.1 is so large that they are virtually two different projects, and our package maintainers become very confused.

[cdown]

Hi! Current development efforts and future plans are focused exclusively on the Rust implementation. As such, the Python version is no longer actively maintained or developed. Anyone interested in a continuation of the Python codebase is welcome to fork it and continue its development independently, but I don't have interest in doing that.

Re: packaging issues, specific examples or details with examples of which distros are impacted would be very helpful. Understanding these challenges more clearly will help me better understand the impact of development decisions on various stakeholders, including package maintainers. As it stands, I'm not immediately seeing how this transition is significantly different from other regular changes to the build system (which package maintainers are generally equipped to handle, even when managing multiple versions). However, I am open to considering alternative evidence that highlights why this particular transition might be uniquely challenging.

Thanks!

[cdown]

I'm closing this for now as no matter the outcome, I won't be maintaining the Python version further. Happy to listen to more details on the packaging issues and which distributions are affected, though.

[ghost]

The python version will thus always remain on the last python version, and will be marked as so on "pypi". And it cannot be removed from there, because there are builds which depend on fetching it from there.

I still suggest moving the rust code into a separate repository, and marking the python version as being "archived".
It is not just "a change of the build system", because for python packages, the "source of truth" is not github but pypi.

[ghost]

Nobody is going to nag you about the issues with the python version if you mark it as "archived", and prohibit creating issues and pull requests.

[cdown]

I don't know why you think that's true, but that's what I did with yturl and I certainly still have been being nagged about it for years :-)