feat: include has_binaries flag in build spec

[AbhinavPradeep]

Summary

Added a has_binaries flag to the build spec. This helps differentiate between pure and non-pure Python wheels.

Description of changes

1. Added a has_binaries flag to the BaseBuildSpecDict.
2. Macaron now defers from generating a dockerfile for non-pure wheels.

[behnazh-w]

Can you please add an integration test for a Python package that includes binaries, to test this new field in the spec?

[behnazh-w]

Suggested change

	#: Flag to indicate if the artifact packages binaries
	#: Flag to indicate if the artifact includes binaries.

[behnazh-w]

Why is this field set here? FYI, this is where we check that a Python package is pure:

• macaron/src/macaron/build_spec_generator/common_spec/pypi_spec.py

  Line 232 in ec37263

  if "any" in wheel_name_platforms:

[AbhinavPradeep]

Currently I have it configured such that with pypi_package_json.wheel(): will throw SourceCodeError if a pure wheel cannot be found. This is because in the current analysis we would not want to analyze non-pure wheels right? So the way I set self.data["has_binaries"] now should be identical to setting it in

macaron/src/macaron/build_spec_generator/common_spec/pypi_spec.py

Lines 232 to 233 in ec37263

	if "any" in wheel_name_platforms:
	patched_build_commands = self.get_default_build_commands(self.data["build_tools"])

.

[behnazh-w]

I'm not sure why self.data["has_binaries"] is set to False here.

[AbhinavPradeep]

Same reason as for other the comment. We only succed a with pypi_package_json.wheel(): if we can find a pure wheel, and therfore on success we can set self.data["has_binaries"] = False.