summaryrefslogtreecommitdiffstats
path: root/Lib/modulefinder.py
Commit message (Collapse)AuthorAgeFilesLines
* SF #841977 - modulefinder fails to find extension modules in packagesThomas Heller2003-11-141-1/+6
| | | | | | | | | | | The find_all_submodules() method in modulefinder only looks for *.py, *.pyc, and *.pyo files. Python extension modules are only found if they are referenced in import statements somewhere. This patch uses the actual list from imp.get_suffixes(). Backported myself.
* up the b/w compatibility requirement to 2.2Just van Rossum2003-07-181-1/+1
|
* Patch #698082 from Thomas Heller: Modulefinder didn't exclude modulesJust van Rossum2003-03-051-4/+4
| | | | in packages correctly.
* Get rid of many apply() calls.Guido van Rossum2003-02-271-2/+2
|
* removed bizarre construct, no idea why it was there...Just van Rossum2003-02-011-1/+0
|
* Whitespace normalization.Tim Peters2003-01-291-3/+3
|
* patch attached to sf item #643711:Just van Rossum2002-12-311-49/+150
| | | | | | | | | | | | | | | | | | | | | any_missing() returns less bogus missing modules. - I've rewritten scan_code() more or less from scratch, factored bits and pieces out for readability. - keep track of global assignments and failed imports per module; use this to determine whether the Y in "from X import Y" is a submodule or just a global name. This is not 100% doable: you can't tell which symbols are imported when doing a star import of a non-Python module short of actually importing it. - added a new method to ModuleFinder: any_missing_maybe(), which returns *two* lists, one with certain misses, one with possible misses. The possible misses are *very* often false alarms, so it's useful to keep this list separate. any_misses() now simply returns the union of any_missing_maybe(). TODO: documentation, test_modulefinder.py
* moving modulefinder.py to the standard libraryJust van Rossum2002-12-311-0/+486