-
Notifications
You must be signed in to change notification settings - Fork 10
Description
[Posting as a new issue as requested in #103 ]
Would you consider making a pypi release? This is quite easy now that there's a good github action for it. You can see an example workflow at https://github.com/SWIFTSIM/swiftgalaxy/blob/main/.github/workflows/python-publish.yml Since you're not already running CI tests on github you could just skip all of the testing bits for now. The workflow is set to run automatically when you create a github release, and can also be run manually (see "workflow dispatch" option). I think that the only trick is that you should create an environment called pypi from the settings page of your repo. Then on the pypi side you set up a "trusted publisher" like:
OpenID Connect publishers associated with swiftgalaxy
Publisher Details
GitHub
Repository: SWIFTSIM/swiftgalaxy
Workflow: python-publish.yml
Environment name: pypi
Since the name caesar is taken on pypi you'd need a different name for the pypi version, but this doesn't need to change the import name. For example I have a package where pip install astromartini and then import martini. The alternative name appears in pyproject.toml as:
[project]
name = "astromartini"
and in the publishing workflow as part of the pypi.org url.
Not mandatory to publish releases on pypi of course, but it is a lot nicer for users, and easier for dependent packages.