Closed KOLANICH closed 1 year ago
I think I'm happy enough with the current situation - we've documented that pep517 is deprecated, and made a legacy
branch to represent it, but we haven't added warnings. If projects are already happy with pep517
does, it's not a problem for them to carry on using it, and if/when they're not happy, it should be easy for them to switch over.
If projects are already happy with pep517 does, it's not a problem for them to carry on using it, and if/when they're not happy, it should be easy for them to switch over.
It causes bloat for 2 copies of the same thing and violates the DRY principle.
Sorry, it just doesn't seem worth getting excited about.
The package was renamed, but too a lot of packages depend on
pep517
.So it is proposed
pep517
branch in this repopep517
package depending onpyproject_hooks
. The package should contain nothing more than aliases to the renamed API and deprecation warnings instructing people to migrate. The ReadMe file should also contain migration instructions.pypi
.