https://bugs.gpodder.org/show_bug.cgi?id=1697
--- Comment #5 from Felix <[email protected]> 2012-10-14 22:05:53 BST --- Created attachment 744 --> https://bugs.gpodder.org/attachment.cgi?id=744 patch for safe_print Well, the "trivial" patch is attached. Note, however, that this is a patch against updated gpo (that is, gpo after 2to3). Which leads me to a bigger question. How flexible you want to be with Python version detection. If there is a separate "gpo3" (3 for version of Python, not of gpo :) ) then version detection isn't necessary. But in such case you may want to clean calls to safe_print, rather have a safe_print translating such calls If, however, you want to have one flexible file, it may be necessary to have something like if sys.version_info >= (3, ): extra['use_2to3'] = True and *force* users to run setup... My background is in PHP, where after a few years it was told "no more PHP4, upgrade to PHP5 or else" - and the community lived happily ever after! So this Python 2 vs 3 dilemma looks a little bit crazy to me. So, I'll let you decide how you want to proceed -- Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
