Build Process - automate publishing to pypi

Question

Build Process - automate publishing to pypi

dougransom opened this issue 2 years ago · 4 comments

@LexiconCode has it publishing to testpypi. A reminder to change to pypi before release.

Answer 1 · 2022-12-27T16:17:39.000Z

I think we are at a point where we could benefit from this. I think the simplest thing is just to change the repository and secret and just publish to pypi whenever the version # is bumped in the main branch.

i noticed we are calling 'python' in the workflow and I wonder if we are supposed to be using "py" instead?

Answer 2 · 2022-12-27T16:19:13.000Z

I would like to use the same workflow in unimacro and vocola and dtactions.

Answer 3 · 2023-01-11T16:47:46.000Z

I have it working on https://github.com/dougransom/unimacro/blob/control_grammars/.github/workflows/python-flit-publish.yml

I plan to use an environment name by default DT_PUBLISH .

Not that workflow is for flit packages, it is just a tweak of the github Publish Python Package workflow, which is meant for setuptools. I also added pulling the python package index from the environment to make switching between pypi and testpypi easier.

Answer 4 · 2023-01-11T17:41:06.000Z

i noticed we are calling 'python' in the workflow and I wonder if we are supposed to be using "py" instead?

In this case it's not necessary as the environment already has python on path with build process environments specific python version. if this was being run locally it would be better to use 'py ' which leverages the python launcher for locating the correct python interpreter.