Fairly often we have accidental unicode issues that are a result of our code using '...' instead of u'...'. And then we come along with a simple fix like https://forge-allura.apache.org/p/allura/git/ci/db076001f36e41d432f03c08da6fe7af785251fe/
If we had `from __future__ import unicode_literals` at the top of the file, then '...' would be unicode by default, instead of str and we wouldn't have these accidental bugs. I'm interested in maybe putting that in all our files. I wonder if anything would break? If we wanted to be even more forward-looking, we could do `from __future__ import absolute_import, division, print_function, unicode_literals` Thoughts? -- Dave Brondsema : [email protected] http://www.brondsema.net : personal http://www.splike.com : programming <><
