zzzeek / sqlalchemy_old / issues / #1713 - clean up assert_unicode — Bitbucket

Issue #1713 resolved

Mike Bayer repo owner created an issue 2010-02-25

likely its best to just have "warn" be the all-the-time setting when any kind of unicode conversion takes place. Document using the warnings filter to raise these into errors.

Comments (4)

Mike Bayer reporter
i.e. and deprecate the assert_unicode flag.
- 2010-02-25T16:32:04+00:00
Mike Bayer reporter
this is in 756370e0b43a20ae30ed03cb30762756c97fb258, then restoring part of it to the Unicode type in 060e30118373c909d4f96f7c3cad2b723fce95ab. Waiting on 2to3 so that we can fix a remaining 3.1 issue.
- 2010-02-25T17:53:20+00:00
Mike Bayer reporter
- changed status to resolved
final tweak c4be0b84a58ec9162c45fc57a6baa9e5fb7c966f.
- 2010-02-25T17:58:19+00:00
Mike Bayer reporter
- removed milestone
Removing milestone: 0.6.0 (automated comment)
- 2014-02-23T18:14:40+00:00
Log in to comment

Assignee: Mike Bayer

Type: bug

Priority: major

Status: resolved

Component: sql

Milestone: –

Votes: 0

Watchers: 0

Jira: the preferred issue tracker for Bitbucket. Join the team!