Changes

would import configparser, htmlparser and xmlrpc client in both python 2 and 3(These are some of the modules used by sugar that I found were relocated in python 3).

would import configparser, htmlparser and xmlrpc client in both python 2 and 3(These are some of the modules used by sugar that I found were relocated in python 3).

Of course just try, except blocks will work just the same, but that code would just feel hacky and ugly. Not to mention that six provides a whole host of other [https://pythonhosted.org/six/ features] like sytax compatibility and is not limited to just wrapping around relocated libraries.

Of course just try, except blocks will work just the same, but that code would just feel hacky and ugly. Not to mention that six provides a whole host of other [https://pythonhosted.org/six/ features] like syntax compatibility and is not limited to just wrapping around relocated libraries.

My project would introduce no new features at all, but it would make sugar future ready and also backwards compatible. It might actually make development/maintenance harder on the core libraries in the short term, because the developers would need to understand the polyglot written using six or ad-hoc polyglot. But it would provide long-term benefits and a wider potential future developer reach.

My project would introduce no new features at all, but it would make sugar future ready and also backwards compatible. It might actually make development/maintenance harder on the core libraries in the short term, because the developers would need to understand the polyglot written using six or ad-hoc polyglot. But it would provide long-term benefits and a wider potential future developer reach.