#2416: Spurious SAWarnings caused by built-in SQL-based auth
------------------------+---------------------------------------------------
Reporter: pitrou | Owner: Gustavo
Type: defect | Status: assigned
Priority: normal | Milestone: 2.1b2
Component: TurboGears | Version: 2.1a1
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by pitrou):
Replying to [comment:7 chrisz]:
>
> I still think repoze.wha.plugins.sql.adapters and repoze.who.plugins.sa
should convert str to
> unicode in the methods mentioned above when they get such input so
SQLAlchemy will not give
> these warnings.
My 2 cents:
I think repoze should not try to do such a conversion. It doesn't know the
charset, the caller (TurboGears) does, so it's up to the caller to do the
conversion.
Sure, repoze can use 'ascii' by default, but this will fool people into
thinking that they're fine and one day they'll have a crash because of
non-ASCII user data.
--
Ticket URL: <http://trac.turbogears.org/ticket/2416#comment:9>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
