[Help wanted] I can't to upload from github to PyPI via github workflow

[benvigano]

This is my package: https://github.com/ben981/scriptifier
I am trying to get it on PyPI using github Actions but when I make a new release, the uploader launches and I get:

Build and publish:
Run python setup.py sdist bdist_wheel
python: can't open file '/home/runner/work/scriptifier/scriptifier/setup.py': [Errno 2] No such file or directory
Error: Process completed with exit code 2.

Am I missing something? Do I need to upload it / create a repository in PyPI before doing this?

[webknjaz]

@ben981 in your script, you are attempting to execute a file called setup.py but it does not exist. This is something that this action does not do, it's all in your workflow. You could either implement packaging setup.py or use a superior PEP 517 compliant method via https://github.com/pypa/build.

[benvigano]

Thak you for the answer! I don't understand because I do have setup.py in my repo.

[webknjaz]

To upload a distribution, you must first create it. That command that is failing is often used to achieve this. But it's out of the scope of this action, we don't attempt to build anything, only upload what you've created. So you must have a step that does this in your workflow followed by using our action.

You don't use our action at all but something that GitHub created in their template. Edit that. Our tutorial is https://packaging.python.org/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/ — it differs from what GitHub offers (their approach is outdated at best).

[benvigano]

Thank you so much! Works perfectly!
It's unbeliavable that GitHub suggests that misleading template, at this point I'd rather they didn't put any template at all.

I successfully uploaded to PyPI, but when I try to push I get

HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
File already exists. See https://pypi.org/help/#file-name-reuse for more information.`

How can I edit the .yml to update the existing package without trying to overwrite it?

[webknjaz]

That is up to you to figure out. Normally, you need to limit when your workflow gets to execute some steps (like upload). Sometimes it's create or release events, or push + check for a tag. But also you need to come up with a mechanism to generate unique versions. I normally use setuptools_scm to source the version from Git tags and make stable releases to PyPI on tag but I also have some clever logic that allows me to push pre-releases on pushes to the main branch to TestPyPI. Although, this is something you'd have to explore and experiment with to fit your specific case.