Sounds like you made good headway, but as you said, worse than expected. I think some of the fixes (e.g. ming) we might want to try to fix upstream (seems like ming should handle unicode names).
Since there's quite a bit of additional work and testing, with minimal benefit (ready for py3 (which far from anyway) and save some unicode interpolation errors)... I'm ok with letting this sit. Unless someone really wants to make it their personal mission :D --- ** [tickets:#7878] Try unicode_literals** **Status:** review **Milestone:** unreleased **Labels:** sf-current sf-2 42cc **Created:** Mon May 18, 2015 03:26 PM UTC by Dave Brondsema **Last Updated:** Wed May 20, 2015 11:39 AM UTC **Owner:** Igor Bondarenko Try `from __future__ import unicode_literals` and possibly `absolute_import, division, print_function` too, in our existing Allura .py files. See what sort of issues may arise. Related email thread starts at http://mail-archives.apache.org/mod_mbox/allura-dev/201504.mbox/%3C553955A5.6020006%40brondsema.net%3E --- Sent from forge-allura.apache.org because [email protected] is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
