On 05/02/15 09:31, Nicola Larosa wrote:
Rob wrote:
Currently we natively support Py2 and support Py3 through 2to3. Fixing
issues in Py3 is quite a hassle like this, but we also do not want to
lose Py2 support yet. How would you feel about using a library like
six to create a codebase that supports both Py2 and Py3 without 2to3?
Rather than six, you want to use future <http://python-future.org/>.
Here's why:
What is the relationship between future and six?
<http://python-future.org/faq.html#what-is-the-relationship-between-future-and-six>
I like the look of future it looks like the most elegant way to do this.
I assume it's pure python so it shouldn't be a too egregious dependency.
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.
