Antoine Pitrou added the comment: > But the current behavior of returning None is documented and people > depend on it so straightening it out would break backward > compatibility - it's up to you to decide. I wouldn't mind it > personally.
I'm not sure people depend on getpeercert() returning None before the handshake is done, or perhaps by accident? > But as far as this ticket goes - I'm on 2.7 and it's set in stone so > for 2.7 - can you please change copy only? If you decide that for > 3.x an exception will be raised then such a caveat would be included > in 2.7 docs as well. Yes, if we change behaviour it will only be in 3.4. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19095> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
