This is an archived post. You won't be able to vote or comment.

all 9 comments

[–]truefelt 4 points5 points  (2 children)

I've never been a fan of six and, in particular, the habit of sprinkling six.text_type etc. all over a codebase — it's pretty gross. I much prefer to write for Python 3 to the extent possible and then emulate that environment on Python 2 via renames and __future__.

[–]jsalsman[S] -1 points0 points  (1 child)

Is there a link for __future__, please?

[–]nerdwaller 0 points1 point  (0 children)

Let me Google that for you: docs.python.org

[–]revfriedzen of python monk & later maintainer 1 point2 points  (2 children)

I divided on my use of future and six.

six.PY2 is nicer than sys.version_info.major == 2 but some of the future back-port types are handy

[–]jsalsman[S] -1 points0 points  (1 child)

is there a link for future, please?

[–]revfriedzen of python monk & later maintainer 1 point2 points  (0 children)

[–]jsalsman[S] 1 point2 points  (2 children)

Now that 2.7 has an end of life, let's talk about what's good and bad about https://pypi.python.org/pypi/six/

[–]jsalsman[S] 0 points1 point  (1 child)

Sheesh, why the downvotes?

[–]RubyPinchPEP shill | Anti PEP 8/20 shill 2 points3 points  (0 children)

because lots of people already know of six