Opened 8 years ago
Last modified 2 years ago
#27778 assigned Cleanup/optimization
Update unicode documentation — at Initial Version
| Reported by: | Aymeric Augustin | Owned by: | nobody |
|---|---|---|---|
| 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 |
| Pull Requests: | |||
Description ¶
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.
According to the ticket's flags, the next step(s) to move this issue forward are:
- To improve the patch as described in the pull request review comments or on this ticket, then uncheck "Patch needs improvement".
If creating a new pull request, include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR].