Re: Aw: Status of ctypes-python bindings
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Fri, 13 Feb 2015 12:30:58 +0000
Andreas Stieger wrote:
I'd be glad to get rid of it, on the basis that it's very far from complete and correct, and doesn't appear to be much used, and that there are alternatives (mainly: swig-python, pysvn, subvertpy).
However, there are probably people making good use of it. It's a bit harsh to delete a feature completely, so close to release, with essentially no time for users to hear and react. If I were a corporate user, with a team making use of it, and it disappeared with essentially no notice, I would be sore. Deprecating it first and then deleting it at the beginning of the next development cycle would be much better.
What is the benefit in deleting it from 1.9, compared with deleting it only from trunk? Is there anything actively hurting us in keeping it around longer, other than the universal burden that all extra code creates?
I would suggest we deprecate it, make it not built by the default "build all bindings" build rules, and give people one minor release in which to migrate off it. Then delete it completely soon *after* branching/releasing 1.9.
Perhaps we could contact the packager of the (one?) known distribution and see what they can tell us? They might be glad to get rid of it, or they might know of particular user groups relying on it.
This is an archived mail posted to the Subversion Dev mailing list.