You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The final challenge here lacks a clear solution where people can have a solid takeaway/reference to understand and refer back to.
The description is still fairly manual but there is the pypa/gh-action-pypi-publish that can be leveraged to make the task somewhat simpler.
I've used this in a couple of packages, you can see example in AFM-SPM/TopoStats. I have an additional set of project.optional-dependencies defined in pyproject.toml in the list pypi which are specifically installed prior to building the package...
In the licensing section, would it be possible to change '..your selection of license may be influenced by the licenses of your dependencies.' to constrained please as it does have a direct impact on choice (or lack of) of licence. All very good though!
The final challenge here lacks a clear solution where people can have a solid takeaway/reference to understand and refer back to.
The description is still fairly manual but there is the pypa/gh-action-pypi-publish that can be leveraged to make the task somewhat simpler.
I've used this in a couple of packages, you can see example in AFM-SPM/TopoStats. I have an additional set of project.optional-dependencies defined in pyproject.toml in the list pypi which are specifically installed prior to building the package...
Also PyPI now supports Trusted Publishers which makes it really simple to configure GitHub/GitLab to publish packages.
@ns-rse thanks for this comment and apologies for the late reply, I must have missed it.
My thought process here was to first demonstrate the manual method of releasing packages before discussing automated workflows. Challenge 3 demos how to automate this. I think my solution was probably too manual, so I'll make it more interactive to rectify this.
The final challenge here lacks a clear solution where people can have a solid takeaway/reference to understand and refer back to.
The description is still fairly manual but there is the pypa/gh-action-pypi-publish that can be leveraged to make the task somewhat simpler.
I've used this in a couple of packages, you can see example in AFM-SPM/TopoStats. I have an additional set of
project.optional-dependencies
defined inpyproject.toml
in the listpypi
which are specifically installed prior to building the package...Also PyPI now supports Trusted Publishers which makes it really simple to configure GitHub/GitLab to publish packages.
The text was updated successfully, but these errors were encountered: