Contain non-ascii str objects in parsers and browser code
Bug #237868 reported by
Jeroen T. Vermeulen
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Colin Watson | ||
Bug Description
doc/potranslati
We should make sure that everything that comes back from the parser or browser code is either unicode or pure-ascii str.
| Changed in rosetta: | |
| importance: | Undecided → Low |
| Changed in rosetta: | |
| status: | New → Triaged |
| tags: |
added: tech-debt removed: cleanup |
| visibility: | private → public |
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| Changed in launchpad: | |
| assignee: | nobody → Colin Watson (cjwatson) |
| status: | Triaged → Fix Released |
To post a comment you must log in.
I fixed all this sort of thing as part of the Python 3 port (enforced even for old code still using the SQLObject compatibility layer, because the Python 3 version of storm.sqlobject