How do I find the location of Python module source

问题:

How do I learn where the source file for a given Python module is installed? Is the method different on Windows than on Linux?

I\'m trying to look for the source of the datetime module in particular, but I\'m interested in a more general answer as well.

回答1:

For a pure python module you can find the source by looking at themodule.__file__. The datetime module, however, is written in C, and therefore datetime.__file__ points to a .so file (there is no datetime.__file__ on Windows), and therefore, you can\'t see the source.

If you download a python source tarball and extract it, the modules\' code can be found in the Modules subdirectory.

For example, if you want to find the datetime code for python 2.6, you can look at

Python-2.6/Modules/datetimemodule.c

You can also find the latest Mercurial version on the web at https://hg.python.org/cpython/file/tip/Modules/_datetimemodule.c

回答2:

Running python -v from the command line should tell you what is being imported and from where. This works for me on Windows and Mac OS X.

C:\\>python -v
# installing zipimport hook
import zipimport # builtin
# installed zipimport hook
# C:\\Python24\\lib\\site.pyc has bad mtime
import site # from C:\\Python24\\lib\\site.py
# wrote C:\\Python24\\lib\\site.pyc
# C:\\Python24\\lib\\os.pyc has bad mtime
import os # from C:\\Python24\\lib\\os.py
# wrote C:\\Python24\\lib\\os.pyc
import nt # builtin
# C:\\Python24\\lib\\ntpath.pyc has bad mtime
...

I\'m not sure what those bad mtime\'s are on my install!

回答3:

I realize this answer is 4 years late, but the existing answers are misleading people.

The right way to do this is never __file__, or trying to walk through sys.path and search for yourself, etc. (unless you need to be backward compatible beyond 2.1).

It\'s the inspect module—in particular, getfile or getsourcefile.

Unless you want to learn and implement the rules (which are documented, but painful, for CPython 2.x, and not documented at all for other implementations, or 3.x) for mapping .pyc to .py files; dealing with .zip archives, eggs, and module packages; trying different ways to get the path to .so/.pyd files that don\'t support __file__; figuring out what Jython/IronPython/PyPy do; etc. In which case, go for it.

Meanwhile, every Python version\'s source from 2.0+ is available online at http://hg.python.org/cpython/file/X.Y/ (e.g., 2.7 or 3.3). So, once you discover that inspect.getfile(datetime) is a .so or .pyd file like /usr/local/lib/python2.7/lib-dynload/datetime.so, you can look it up inside the Modules directory. Strictly speaking, there\'s no way to be sure of which file defines which module, but nearly all of them are either foo.c or foomodule.c, so it shouldn\'t be hard to guess that datetimemodule.c is what you want.

回答4:

The sys.path list contains the list of directories which will be searched for modules at runtime:

python -v
>>> import sys
>>> sys.path
[\'\', \'/usr/local/lib/python25.zip\', \'/usr/local/lib/python2.5\', ... ]

回答5:

If you\'re using pip to install your modules, just pip show $module the location is returned.

回答6:

datetime is a builtin module, so there is no (Python) source file.

For modules coming from .py (or .pyc) files, you can use mymodule.__file__, e.g.

> import random
> random.__file__
\'C:\\\\Python25\\\\lib\\\\random.pyc\'

回答7:

from the standard library try imp.find_module

>>> import imp
>>> imp.find_module(\'fontTools\')
(None, \'C:\\\\Python27\\\\lib\\\\site-packages\\\\FontTools\\\\fontTools\', (\'\', \'\', 5))
>>> imp.find_module(\'datetime\')
(None, \'datetime\', (\'\', \'\', 6))

回答8:

In the python interpreter you could import the particular module and then type help(module). This gives details such as Name, File, Module Docs, Description et al.

Ex:

import os

help(os)


Help on module os:

NAME

os - OS routines for Mac, NT, or Posix depending on what system we\'re on.

FILE

/usr/lib/python2.6/os.py

MODULE DOCS

http://docs.python.org/library/os

DESCRIPTION

This exports:

- all functions from posix, nt, os2, or ce, e.g. unlink, stat, etc.

- os.path is one of the modules posixpath, or ntpath

- os.name is \'posix\', \'nt\', \'os2\', \'ce\' or \'riscos\'

et al

回答9:

New in Python 3.2, you can now use e.g. code_info() from the dis module: http://docs.python.org/dev/whatsnew/3.2.html#dis

回答10:

Check out this nifty \"cdp\" command to cd to the directory containing the source for the indicated Python module:

cdp () {
  cd \"$(python -c \"import os.path as _, ${1}; \\
    print _.dirname(_.realpath(${1}.__file__[:-1]))\"
  )\"
}

回答11:

Here\'s a one-liner to get the filename for a module, suitable for shell aliasing:

echo \'import sys; t=__import__(sys.argv[1],fromlist=[\\\".\\\"]); print(t.__file__)\'  | python - 

Set up as an alias:

alias getpmpath=\"echo \'import sys; t=__import__(sys.argv[1],fromlist=[\\\".\\\"]); print(t.__file__)\'  | python - \"

To use:

$ getpmpath twisted
/usr/lib64/python2.6/site-packages/twisted/__init__.pyc
$ getpmpath twisted.web
/usr/lib64/python2.6/site-packages/twisted/web/__init__.pyc

回答12:

On windows you can find the location of the python module as shown below:i.e find rest_framework module

回答13:

On Ubuntu 12.04, for example numpy package for python2, can be found at:

/usr/lib/python2.7/dist-packages/numpy

Of course, this is not generic answer

回答14:

Not all python modules are written in python. Datetime happens to be one of them that is not, and (on linux) is datetime.so.

You would have to download the source code to the python standard library to get at it.

回答15:

For those who prefer a GUI solution: if you\'re using a gui such as Spyder (part of the Anaconda installation) you can just right-click the module name (such as \"csv\" in \"import csv\") and select \"go to definition\" - this will open the file, but also on the top you can see the exact file location (\"C:....csv.py\")

回答16:

You can see source right from the git repository. For example here is the datetime module and as a bonus, the subprocess module.

If you do more digging around you can find the traditional implementation of the standard Python interpreter, which is written in ‘C’ and also called ‘CPython’