Opened 5 years ago

Closed 5 years ago

#20831 closed Bug (invalid)

unicode() is a function, not a type

Reported by: German Larrain Owned by: nobody
Component: Documentation Version: master
Severity: Normal Keywords: python3
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no


In "Porting to Python 3 / Moved modules".

Submitted pull request

Change History (5)

comment:1 Changed 5 years ago by Tim Graham

The docs are correct. Perhaps we should replace the :func:`unicode` markup with ``unicode`` though, as the link may be misleading.

comment:2 Changed 5 years ago by German Larrain

timo, I thinks it's either

:func:`unicode` function


:class:`unicode` type

but the rest of the sentence goes on about functions (I think), not types. Anyways, it's just a matter of making it consistent.

comment:3 Changed 5 years ago by Aymeric Augustin

We'll replace it with str shortly too :)

comment:4 Changed 5 years ago by Tim Graham

:class:`unicode` doesn't create a valid link. Later in the sentence :func:basestring() is mentioned, which is an "abstract type" but requires the :func: prefix to link correctly. I'd say we should leave everything as is, or simply remove the links if they cause confusion. When we update the Django interphinx mapping to point to Python 3 rather than 2, I imagine we'll have to remove these links at that time anyway.

comment:5 Changed 5 years ago by Tim Graham

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.
Back to Top