(original) (raw)
I have to agree with Antoine -- I don't think there's a shortcut that avoids \*someone\* actually having to understand the code to the point of being able to recreate the same behavior in the different context (pun not intended) of Python 2.
On Tue, Jul 1, 2014 at 1:54 PM, Antoine Pitrou <antoine@python.org> wrote:
Le 01/07/2014 14:26, Alex Gaynor a écrit :I don't think this makes much sense; Mercurial won't be smarter than you are. I think you'd have a better chance of succeeding by backporting one feature at a time. IMO, you'd first want to backport the \_SSLContext base class and SSLContext.wrap\_socket(). The latter \*will\* require some manual coding to adapt to 2.7's different SSLSocket implementation, not just applying patch hunks around.
I can do all the work of reviewing each commit, but I need some help from a
mercurial expert to automate the cherry-picking/rebasing of every single
commit.
What do folks think? Does this approach make sense? Anyone willing to help with
the mercurial scripting?
Regards
Antoine.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org
--
--Guido van Rossum (python.org/\~guido)