02strich
Clarify compatibility with https://pypi.python.org/pypi/kerberos
So looks like you forked from bgamble/pykerberos which looks like a copy from kerberos from the svn repository. Can you please clarify the compatibility of both projects? Background is that both install a kerberos.so (so yours and the one from pypi called kerberos) so it's not possible to install both in parallel. And that's a problem for distributions. So is it possible to a) merge your changes into the original code or b) clarify if both projects are exchangeable/compatible or c) rename your extension to pykerberos.so ?
The projects are API compatible, with this one containing a slightly different set of fixes and platform compatibility.
The original code base was abandoned for quite a while and Apple has only recently resumed work on it.
Having all that said, renaming the binary to make it more straightforward to install sounds like a good idea nevertheless.
Renaming the so from kerberos.so to pykerberos.so is going to break every application that currently uses this package.
Renaming the so from kerberos.so to pykerberos.so is going to break every application that currently uses this package.
yeah. so best would be to remerge the 2 projects...
It looks like Apple is actively developing pykerberos again (and releasing on pypi). They just did a release January 25.
https://pypi.python.org/pypi/kerberos http://www.calendarserver.org/log/PyKerberos/trunk?rev=15501
Renaming the so does not necessarily break every current user as a python shim could be provided redirecting the call and emitting a warning.
Alternative to the python-level shim, I could bump the major version number and rename the library. At this point I fear that merging with upstream or another fork is going to be quite hard due to changes in all alternative variants.
Taking a step back and having a look at the larger picture, there are now more advanced kerberos bindings for Python available then this one and I am less then certain that it is worthwhile to keep maintaining this project anymore.
there are now more advanced kerberos bindings for Python available
I'm curious which libraries are you referring to?
@ktdreyer https://github.com/pythongssapi/python-gssapi is one of them. A few people are actively looking at merging ccs-pykerberos with this fork but so far this is being used by some libraries like Ansible to add Kerberos support for Windows. I don't think this will be abandoned anytime soon but I would recommend you look at python-gssapi instead.
@ktdreyer development work on the original python kerberos library has been resumed by Apple with people being able to invest more time into it then I was able to invest this fork. Since writing the above note, others have come forward to help with the maintenance of this fork though it is safe to say it will stay around (while maybe being merged with another implementation for even better support).