This is still anecdotical, but most python developers I know would chose py2 if given the choice. It's what they know, and they don't want to change semantics even if it's just changing how you write prints.
Counter-anecdote: Not a single developer I know wants to touch Python 2 after trying to get Django to work reliably with Unicode.
Then again, if your language is completely representable with US-ASCII, you might not have experienced the pain caused by having to unit test pretty much all string operations in your code.
I like to trot out this link whenever this comes up [1].
[1]: https://semaphoreci.com/blog/2016/11/11/python-versions-used...
> I understand this is purely anecdotal, but it seems outlandish to say that Python devs mostly use Python 2.
Then I guess it's a good thing I didn't say that. I said the majority of the ones I know use it.
Sure, lots of Enterprise apps use Python 2 because that was what they could build with.
I'm a Python developer and I don't know anyone who doesn't use Python 3 by default.
I understand this is purely anecdotal, but it seems outlandish to say that Python devs mostly use Python 2.