You can clone with
HTTPS or Subversion.
Very very nice work done in Flask! Really liked it!
However, I was trying to run my Flask script under a subfolder of my Desktop folder in Ubuntu. Since my system is set up for Portuguese (I'm Brazilian), the default name for the folder is "Área de Trabalho". I was getting UnicodeEncodeError every time I tried to run the example in "11.7 Uploading Files". (At least it was really good to teach me how to use the Flask debugger!) I went around, examining where the error was coming from, and, finally, got to "File "/usr/local/lib/python2.6/dist-packages/Flask-0.6-py2.6.egg/flask/helpers.py", line 350, in send_file", when the function adler32 uses the unicode string. Then, I just tried a quick "from zlib import adler32; adler32(u'Á')" to realize that zlib doesn't allow unicode strings, returning a "UnicodeEncodeError: 'ascii' codec can't encode character u'\xc1' in position 0: ordinal not in range(128)".
Of course I can move my script to another folder, but it would be nice not having to think about that in the future, especially when it is said that "Flask like Jinja2 and Werkzeug is totally Unicode based when it comes to text".
Sorry if I don't make much sense... it's almost 3:00am around here...
Congrats for the great job on Flask!
Heh. I really should have included an exception for "except for filesystem access". The reason for this being that it's close to impossible to support unicode file access on POSIX systems. But it's definitively something that should be improved, just that it's damn hard to get it right.
What about wrapping path operations like this?
return os.path.join(directory, filename)
encoding = sys.getfilesystemencoding()
d, f = [x if isinstance(x, unicode) else unicode(x, encoding) for x in (directory, filename)]
return os.path.join(d, f)
I encounter the problem and fixed by:
create database xxx default character set utf8 default collate utf8_gerneral_ci
set names 'utf8' colate 'utf8_general_ci'
in sqlalchemy connection uri:
then it works well in Jinja2
It would be extremely useful if we fix this problem or add a comment to the documentation that tells the user not to use a path that contains characters other the ascii charset.
If you point me in the right direction I can add the comment to the documentation.