# This is the 1st commit message:

ENH: wheel: attempt to build with pep517

# This is the commit message #2:

:art:

I would prefer to leave this in, but I just know that someone will complain about it.

Since cleaning is not defined behavior, just skip it and mark the clean function as deprecated

In accordance with the specification, setuptools doesn't generate
an egg_info directory that we can read in PEP 517 mode. We therefore
switch the directories to something that works.

PEP 517 requires a newer setuptools version, which we need
to install in order to run the setuptools backend so that
we don't have to call setup.py.

…iled

Use `pkg_resources.DistInfoDistribution` so metadata is correctly handled.

This test did not succesfully test the PEP 518 specification in the
first place and the reason for its failure is related to how the testing
framework sets up dependency links, which has very little bearing
on how this will actually be used (dependencies will be downloaded
from pypi in almost all cases).

Python 2.7 doesn't support the "-I" option, so we remove
it if we're running on that verion.

In some cases the metadata directory was poorly specified,
and the path was relative, and the directory already 
existed. We simply remove the directory here if it exists and
specify an absolute path.

Here, we apply a temporary patch to setuptools that will be in the next
release. In addition, we make some small fixes, mostly related to output
to fix the tests.

The setuptools backend doesn't correctly handle the output of
subdirectories (issue will be addressed in setuptools). We updated
the patch with the upstream fixes.

The setuptools backend doesn't correctly handle the output of
subdirectories (issue will be addressed in setuptools). We updated
the patch with the upstream fixes.

The PEP 517 backend runs the dist_info command,
so we expect that.