> Seems like we should revert r62242 test_ssl.py in py3k, commit that, then c= > opy it back to trunk, manually 3to2 it, then check that in, then block that= > particular revision. Then, going forward, if test_ssl.py changes need to = > be made, make them against trunk, and they'll get picked up in the regular = > merges to py3k. > > Sound like a plan?
Yep. Thanks for looking through this. Bill _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
