Would you consider releasing wheels for seqeval on Pypi as well as sdist releases?
Pitch
This would make installing neo4j much easier for me in a specific corporate environment (at AstraZeneca, who have an enterprise license), as at the moment, the fact that neo4j requires setuptools at setup causes pip to execute without a proxy when building neo4j, as the proxy isn't passed through with PEP-517 build isolation - see this issue: https://github.com/pypa/pip/issues/7805 . If neo4j was distributed as a wheel, this would sidestep the issue (as the package would already be built when downloaded).
Feature Request
Hi,
Would you consider releasing wheels for seqeval on Pypi as well as sdist releases?
Pitch
This would make installing neo4j much easier for me in a specific corporate environment (at AstraZeneca, who have an enterprise license), as at the moment, the fact that neo4j requires setuptools at setup causes pip to execute without a proxy when building neo4j, as the proxy isn't passed through with PEP-517 build isolation - see this issue: https://github.com/pypa/pip/issues/7805 . If neo4j was distributed as a wheel, this would sidestep the issue (as the package would already be built when downloaded).