From 04d1816de00226c960bea7d07e3cb1f538d1b44a Mon Sep 17 00:00:00 2001 From: hauntsaninja <> Date: Tue, 13 Oct 2020 11:17:38 -0700 Subject: [PATCH] setup.py: use find_packages 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 --- setup.py | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/setup.py b/setup.py index b6d8b54cff74..c3f2fa178d72 100644 --- a/setup.py +++ b/setup.py @@ -15,7 +15,7 @@ # This requires setuptools when building; setuptools is not needed # when installing from a wheel file (though it is still neeeded for # alternative forms of installing, as suggested by README.md). -from setuptools import setup +from setuptools import setup, find_packages from setuptools.command.build_py import build_py from mypy.version import __version__ as version from mypy import git @@ -178,11 +178,7 @@ def run(self): license='MIT License', py_modules=[], ext_modules=ext_modules, - packages=[ - 'mypy', 'mypy.test', 'mypy.server', 'mypy.plugins', 'mypy.dmypy', - 'mypyc', 'mypyc.test', 'mypyc.codegen', 'mypyc.ir', 'mypyc.irbuild', - 'mypyc.primitives', 'mypyc.transform', 'mypyc.analysis' - ], + packages=find_packages(), package_data={'mypy': package_data}, scripts=['scripts/mypyc'], entry_points={'console_scripts': ['mypy=mypy.__main__:console_entry',
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.
Alternative Proxies: