unicode() is a function, not a type

[German Larrain]

In "Porting to Python 3 / Moved modules".

Submitted pull request ​https://github.com/django/django/pull/1415

[Tim Graham]

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

[German Larrain]

timo, I thinks it's either

:func:`unicode` function

or

: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.

​https://docs.djangoproject.com/en/dev/topics/python3/#string-handling

[Aymeric Augustin]

We'll replace it with str shortly too :)

[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.