Hello Ryan, You are right, Python 2 to 3 code migration may be accomplished in part by employing tools such as modernize <https://python-modernize.readthedocs.io/en/latest/>, futurize <https://python-future.org/automatic_conversion.html> and 2to3 <https://docs.python.org/2/library/2to3.html>, but the resulting, automatically converted code needs to be revised and in rewritten in places, as ambiguous semantic differences are to be expected. Your overall optimistic view on migration should prove in the end justified.
-- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7289a9c4-6580-46a4-abed-0ca53275e299%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.