If you use Django on Leopard, you might encounter a strange “Locale UTF-8 not found” error when running your application. This is due to a bug in Terminal.app, albeit an easy to fix one: just go to the Preferences pane / “Settings” page / “Advanced” tab and uncheck the “Set LANG environment variable on startup” checkbox. Reopen your Terminal session, load the Django application and voilà! Your bug has disappeared. The screenshot below might help too:
Hope this helps!
PS: yes, I’m doing Django and hence Python these days ;)
Similar Posts:
- Starting with Django in Leopard
- 15 Startup Commandments, by Mark Fletcher
- Install MySQL_python in Leopard
- Rails vs. Django
- My first Django project
- Subscribe to comments!
- Quick spec from your Python tests
3 Comments
01.09.2008
I love the new screenshots you can get in Leopard, with shadows included, they’re simply gorgeous!!! :)
01.17.2008
Does any statistics exist about the time lost by developers fixing encoding characters bugs or wrong transcoding behaviour? Definitely character encoding is not yet resolved, despite of UTF…it’s a pity to see that in 2008 developers should still loose time dealing with character encoding issues instead of developing sexy features…
01.19.2008
Well, I can tell you that 10 years ago, dealing with multiple languages was a mess (much more than it is now, I mean). Where I used to work in Argentina at that time we did a website in Spanish, English, Russian and Japanese. I cannot tell you how much it would have helped to have UTF-8 support in both the SQL Server 6.5 database we used at the time, and in the M$ ASP pages infrastructure (with horrid VBScript in them). Even if it’s still not 100% perfect today, it’s much, much better anyway.
Thanks for your comments!
Commenting