Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Delete pyproject.toml to work around pip bug #6342
Feb 5, 2019
Excellent. We'll revert this once there is a pip 19 release that defaults to using the legacy backend.
(We could directly ask to use it ourselves, but that seems dodgy since it has a bunch of underscores in the name and would make us require a very recent setuptools ourselves)
The main reasons for making it underscore is because importing from setup.py is considered a bad practice, not necessarily because it's actually dodgy using it.I think if we do want to really on importing from setup.py the version we might as well be upfront about it. I'll link in the discussion about the subject tomorrow. I'm not sure if pip will default to it though, AFAIK the intention is to be more like a bailout mechanism for packages who do want this behaviour.