See http://docs.python.org/library/email.mime.html

Inside MIMEApplication documentation, link to MIMEApplication is enabled
but link to MIMENonMultipart is disabled. This happens because
MIMENonMultipart is not in email.mime.application (specified by
currentmodule directive). Is this sphinx bug? Or should MIMENonMultipart
be written in full name like email.mime.nonmultipart.MIMENonMultipart?

Since NonMultipart is in another module, it is not found automatically
by unqualified name.  This is working as expected.

Sorry, I shouldn't call this a bug. Rather I should use the word
"proposal". I think a link to MIMENonMultipart is also useful. What I
can imagine how to achieve this is...

1. Rewrite MIMENonMultipart to email.mime.MIMENonMultipart
2. Introduce something new directive to sphinx? Like :class<email.mime>:
3. When class is not found in current module, search in document global
module.

How do you think?

You can write :class:`~email.mime.MIMENonMultipart`; this will link to
the correct class but only display the thing after the last dot, in this
case "MIMENonMultipart".

Thanks, I'll create the patch using this.

I noticed :meth:`~email.message.Message.add_header` renders "add_header"
but maybe "Message.add_header" is better? (Maybe sphinx tracker is
suitable for now....)

If you want that level of control, it may be better to just write
:meth:`Message.add_header() <email.message.Message.add_header>`.