Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes: > > (i also find "notmuch2" rather unsatisfying, but python doesn't have a > meaningful versioning system for backwards-incompatible API changes for > its modules, so this kind of name augmentation is the only strategy i'm > aware of). Naming is hard. What about "notmuch3" to hint that it's for python3? A transition plan could be to have notmuch load the new bindings, after a deprecation period. d _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch