Update pypi publishing

[f-hafner]

Description

• I have read the contribution guidelines
• This update is in line with what is recommended in the Python chapter of the Guide

This proposes a fix to #372.

I just now realise #373 asks for a workflow. I had also wondered whether I should add that. For now, it's just in the sample code in the README.dev.md file. I can transfer this into a workflow file -- can you give some feedback on the sample code? I copied from a workflow that works, but perhaps you have suggestions for improvement.

[f-hafner]

• I've added a workflow file.
• tests fail because of Bumpversion bug #377

[fdiblen]

Hey @f-hafner ,

The template is using copier now. Will you have time to update and complete this PR?

[f-hafner]

@fdiblen , I have to get familiar with the new template but I can work on this

[fdiblen]

@fdiblen , I have to get familiar with the new template but I can work on this

I think it makes more sense to close this pull request and create a new one. I will close this PR. Please let us know if you need help with creating a new one.

[egpbos]

Was it really necessary to close this? It seemed like the merge conflicts were minor, especially because one file is completely new.

[JaroCamphuijsen]

@f-hafner @fdiblen I was working with a project based on the template today and was really surprised the automated PyPI publishing workflow is not yet in there, is it ok if I pick this up and add the workflow file to the template? The current 3-step manual release instructions feel quite outdated.

[fdiblen]

Hi @JaroCamphuijsen

I am not actively working on this project anymore and not up to date with the recent changes. But, I would be careful about complete automation as users may need to take a few more steps such as check Zenodo integration, test the package etc.

@sverhoeven and @abelsiqueira may help you deciding the best way forward.

[abelsiqueira]

I like the idea, and I think @f-hafner won't mind if you take it over, but I haven't been working on the Python template.
I know @sjvrijn was spending some time maintaining it, so he has a better view of where it is going at the moment.
That said, I think it fits in the template because you can make auto-publishing to pypi optional and not part of the default recommendation in copier.

[sjvrijn]

@JaroCamphuijsen Go ahead!

[wschuell]

Hi @JaroCamphuijsen , what is the status of your attempt ? As mentioned in my recent issue, I made a fork and implemented it for our team (for copier); but kinda rudimentarily: https://github.com/wschuell/python-template/blob/databases/template/%7B%25%20if%20HasWorkflows%20%25%7D.github%7B%25%20endif%20%25%7D/workflows/%7B%25%20if%20AddPyPI%20%25%7Dpublish.yml%7B%25%20endif%20%25%7D.jinja

Let me know if you want to coordinate or if you re close to shipping your own PR