Message5392
Which at this point is just the unicode issue (http://issues.roundup-tracker.org/issue2550811)
right? Issue 2550847 is closed and issue 2550848 is still marked as new, but the last comment
says "Commit 63c31b18b955 fixes this issue", so maybe it should be closed?
Reading through the comments on the unicode issue, it seems like it was left somewhat
ambiguous as to whether there would just be a "hack" for the 1.5.1 release (since it only
really affected jinja2) or if a "real" fix would be necessary before the release. Is this
still up in the air? |
|
Date |
User |
Action |
Args |
2015-12-02 20:01:58 | kerrigan@naturescapelawncare.com | set | messageid: <1449086518.85.0.307838718332.issue2550863@psf.upfronthosting.co.za> |
2015-12-02 20:01:58 | kerrigan@naturescapelawncare.com | set | recipients:
+ kerrigan@naturescapelawncare.com, schlatterbeck, ber, techtonik, jerrykan |
2015-12-02 20:01:58 | kerrigan@naturescapelawncare.com | link | issue2550863 messages |
2015-12-02 20:01:58 | kerrigan@naturescapelawncare.com | create | |
|