Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #64795
| Date | 2014-01-26 15:29 +0100 |
|---|---|
| From | lgabiot <laurent.gabiot@gmail.com> |
| Newsgroups | comp.lang.python |
| Subject | Re: Can't get sqlite3.Row working: keyword lookup doesn't work |
| References | <52e46bf3$0$2378$426a34cc@news.free.fr> <mailman.5990.1390723532.18130.python-list@python.org> |
| Message-ID | <mailman.6003.1390769554.18130.python-list@python.org> (permalink) |
Le 26/01/14 09:05, Peter Otten a écrit : > Please remember to cut and past the traceback next time. > >> What is wrong? > > My crystal ball says that you have a > > from __future__ import unicode_literals > > statement at the beginning of the module. If I'm right try > > row[b"filename"] Thanks a lot for your answer! your crystal ball was completely right, indeed I use the __future__ import, and the b'' fixed everything. Three days I was trying to get this...
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Can't get sqlite3.Row working: keyword lookup doesn't work lgabiot <lgabiot@hotmail.com> - 2014-01-26 02:59 +0100
Re: Can't get sqlite3.Row working: keyword lookup doesn't work Peter Otten <__peter__@web.de> - 2014-01-26 09:05 +0100
Re: Can't get sqlite3.Row working: keyword lookup doesn't work lgabiot <lgabiot@hotmail.com> - 2014-01-26 15:29 +0100
Re: Can't get sqlite3.Row working: keyword lookup doesn't work lgabiot <laurent.gabiot@gmail.com> - 2014-01-26 15:29 +0100
csiph-web