Given that one of twine's dependencies now has a dependency on Rust, I have decided to remove the pypi repository publish stage from the Jenkinsfile for now.
I investigated some alternatives, namely poetry and flit. Both of these would require some significant changes to our current build process and package metadata. If we are unable to find a way to get twine working, maybe it could be worth investigating these further when we are ready to start publishing to pypi since they both seem to work on z/OS with no issues.
:pager: Implementation Details
Remove section from Jenkinsfile that does pypi repository upload using twine.
Remove twine from development dependencies
Update README to point to GitHub releases for downloading and installing pyRACF.
Updates to package metadata.
Make package name lowercase.
Update classifiers.
:clipboard: Is there a test case?
Again, the Jenkins server being used is internal, however, after removing the pypi repository upload stage with twine, everything else still works with no issue.
:bulb: Issue Reference
N/A
:computer: What does this address?
Given that one of twine's dependencies now has a dependency on Rust, I have decided to remove the pypi repository publish stage from the Jenkinsfile for now.
I investigated some alternatives, namely poetry and flit. Both of these would require some significant changes to our current build process and package metadata. If we are unable to find a way to get twine working, maybe it could be worth investigating these further when we are ready to start publishing to pypi since they both seem to work on z/OS with no issues.
:pager: Implementation Details
:clipboard: Is there a test case?
Again, the Jenkins server being used is internal, however, after removing the pypi repository upload stage with twine, everything else still works with no issue.