3 ms·
If I were the maintainer, I would create cryptography2 and put the original cryptography into the bugfix mode. It is time to move to a safer language, but break
by acmj 6y ago
If I were the maintainer, I would create cryptography2 and put the original cryptography into the bugfix mode. It is time to move to a safer language, but breaking backward compatibility is always bad.
- epage 6y agoWhat is breaking backward compatibility? Using new python features? Using new C features? Bug fixes? To have any sanity as a maintainer, you have to draw the line somewhere.
- AlphaSite 6y agoIt’s continued to support the architectures which it promises to support and its API compatible. I don’t think making a change which breaks a third party, out of tree, port is breaking backwards comparability, this feels more like someone depending on internal implementation details.