Opened 8 years ago
Last modified 21 months ago
#27778 assigned Cleanup/optimization
Update unicode documentation for Python 3
| Reported by: | Aymeric Augustin | Owned by: | Basant Babu Bhandari |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
The "Unicode data" page doesn't make sense for people who started on Python 3 and who have always had the luxury of a str type that works.
Also it assumes that Python's default charset is ASCII, while it is UTF-8 now.
This page should be renamed to "Encoded data" and, instead of explaining how unicode strings are different from (Python 2) regular strings, it should explained how encoded strings are different from (Python 3) regular strings and how external systems deal with them.
There's also a handful of references to "Unicode strings" in other documentation pages that should be changed to just "strings".
Change History (13)
comment:1 by , 8 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 8 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:4 by , 8 years ago
| Summary: | Update unicode documentation → Update unicode documentation for Python 3 |
|---|
comment:5 by , 8 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:6 by , 8 years ago
| Has patch: | set |
|---|---|
| Patch needs improvement: | set |
A PR starts this but hasn't done much rewriting yet.
comment:11 by , 3 years ago
| Owner: | removed |
|---|---|
| Status: | assigned → new |
Note:
See TracTickets
for help on using tickets.
This PR is dealing with the unicode term replacement with "string". But as I commented on the PR, the "Unicode data" page does indeed need to be rewritten.