Skip to content

Commit 1b21080

Browse files
authored
setup.py: use find_packages (#9593)
Is there a reason to not do this? It gets the right set of packages when I run it. Saves chores like #9587 or #9061
1 parent e21214f commit 1b21080

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

setup.py

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@
1515
# This requires setuptools when building; setuptools is not needed
1616
# when installing from a wheel file (though it is still neeeded for
1717
# alternative forms of installing, as suggested by README.md).
18-
from setuptools import setup
18+
from setuptools import setup, find_packages
1919
from setuptools.command.build_py import build_py
2020
from mypy.version import __version__ as version
2121
from mypy import git
@@ -178,11 +178,7 @@ def run(self):
178178
license='MIT License',
179179
py_modules=[],
180180
ext_modules=ext_modules,
181-
packages=[
182-
'mypy', 'mypy.test', 'mypy.server', 'mypy.plugins', 'mypy.dmypy',
183-
'mypyc', 'mypyc.test', 'mypyc.codegen', 'mypyc.ir', 'mypyc.irbuild',
184-
'mypyc.primitives', 'mypyc.transform', 'mypyc.analysis'
185-
],
181+
packages=find_packages(),
186182
package_data={'mypy': package_data},
187183
scripts=['scripts/mypyc'],
188184
entry_points={'console_scripts': ['mypy=mypy.__main__:console_entry',

0 commit comments

Comments
 (0)