Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Hi,
Would you consider releasing wheels for seqeval on Pypi as well as sdist releases?
Travis only uploads a source distribution ('sdist') by default to Pypi (see here: https://docs.travis-ci.com/user/deployment/pypi/#uploading-different-distributions). Adding wheel as well.
In particular, this would make installing seqeval much easier for me in a specific corporate environment, as at the moment, the fact that seqeval requires setuptools_scm at setup causes pip to execute without a proxy when building seqeval, as the proxy isn't passed through with PEP-517 build isolation - see this issue: pypa/pip#7805 . If seqeval was distributed as a wheel, this would sidestep the issue (as the package would already be built when downloaded).
I believe this PR should be the correct way to distribute seqeval as a wheel using Travis, but I haven't used Travis much myself, so this probably would require testing on your side. Let me know if you would rather me make an issue than a PR if this doesn't work straight away.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
No testing - it's unclear to me how I can test this without access to the Travis CI for seqeval. If there is some way I can test though I'd be happy to.
Checklist: