add pythonpublish.yml
Note: This requires a GitHub secret PYPI_API_TOKEN, which is up to the maintainers to configure.
This publishes to PyPi whenever a release is created, based on the Git tag associated with that release.
Closes #1154
Thanks for this. I need to work out how to fit this into the rest of our release process, so won't be merging very quickly. I really do appreciate the leg-work here though.
Just as a heads-up: PyPI nowadays recommends using Trusted Publishers instead of token-based authentication: https://docs.pypi.org/trusted-publishers/using-a-publisher/
Yes, there have been changes in the meantime. I can update it, but I'm not sure there's interest from the maintainers since none of my PRs got through
Thanks @FriedrichFroebel, the extra information is always appreciated.
@sigma67 the maintainers are volunteers with a large number of other commitments and limited Python expertise. We do appreciate your input in the project, but I do not find your remark about a lack of interest either constructive or helpful.
@lornajane I am in the same position as an OSS maintainer myself with a full time job. Yet I manage to respond to PRs within weeks at the latest
I have submitted two PRs to this project and neither have received feedback within the past 12 months
I realize you may have more important issues on the table, but responding as you did after all this time is disrespectful of the contribution itself, honestly. Not surprised there are no external contributors other than the maintainers
If you do not want contributions, please say so - for now I will close this.