Originally reported by: ostcar (Bitbucket: ostcar, GitHub: ostcar)
Your documentation defines, that the MANIFEST.in is only parsed, if include_package_data is set to True. So I suppose it is not read if include_package_data is set to False. That works fine for the 'build' or 'bdist' command. But the sdist commands includes parses the MANIFEST.in even if include_package_data is set to False.
This could probably be fixed in the method commands.egg_info.manifest_maker.run
by changing the line if os.path.exists(self.template) to if os.path.exists(self.template) and self.distribution.include_package_data:
Originally reported by: ostcar (Bitbucket: ostcar, GitHub: ostcar)
Your documentation defines, that the MANIFEST.in is only parsed, if include_package_data is set to True. So I suppose it is not read if include_package_data is set to False. That works fine for the 'build' or 'bdist' command. But the sdist commands includes parses the MANIFEST.in even if include_package_data is set to False.
This could probably be fixed in the method
commands.egg_info.manifest_maker.runby changing the line
if os.path.exists(self.template)toif os.path.exists(self.template) and self.distribution.include_package_data: