Support variable definitions in literalinclude's pyobject option

[torfsen]

The :pyobject: option of the literalinclude directive is great for including only a specific definition of a module. Currently (Sphinx 1.8.4), it supports class and function definitions. I suggest to extend this to also support module-level variable definitions.

An example from my personal use case: I use collections.namedtuple in my code for creating simple record-like classes:

MyClass = namedtuple('MyClass', 'attribute1, attribute2')

Since they don't use a "real" class definition, I cannot show their definition using :pyobject:.

A possible alternative to supporting variable definitions in :pyobject: which might be more flexible would be to support grepping lines using a regex. I could then do

.. literalinclude:: my_module.py
   :regex: ^MyClass\s*=

[tk0miya]

+0 for supporting module level variable: Reasonable. I can accept if somebody sends us a PR.
-1 for adding new option: The directive is already too much complicated. And the notation seems like a program.

[tk0miya]

Note: we have to investigate the way to know the whole of lines of assignment. An assignment statement might be during mulptiple lines:

foo = (1,
       2,
       3)