On 12/19/06, Damjan <[EMAIL PROTECTED]> wrote:
> Are we on the same page, or am I still lost? Not lost at all :)
Ah, good :-D
Except I'd prefer if all Python API's would be unicode aware,
I think it's fortunate that most Python APIs *can* ignore the unicode problem. As a stupid American, I'm glad that *most* of my code *just works*. Every once in a while, I have to pay attention. I think that's okay. Imagine a Python function: def concat(strings): return "".join(strings) Such a function works with str or unicode. I'm glad that I don't have to think about unicode when I write functions like that.
and would not encode/decode until it's utmost necessary.
Agreed.
I think it would be nice if the Python DB-API is reviewed and make unicode a requirement (for quieries and results).
I think you should bring this up on the Python DB-SIG. I don't know what their plans are.
This would be inline with the P3K efforts. And I think that most dB drivers today do support unicode, MySQLdb obviously, psycopg2 and pysqlite2 IMHO support unicode too. So I don't think SQLAlchemy should do the encode/decode'ing unless the underlaying driver doesn't support unicode.
It would be fine if the DB API specified Unicode. Until it does, I'm glad SQLAlchemy can "just take care of the problem", at least when MySQLdb isn't broken ;) Happy Hacking! -jj -- http://jjinux.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
