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
Using PyPA's own Flit would be much simpler to adapt since the repo is still a clean slate as far as packaging automation goes. Most notably, Flit would only require setting the environment variables FLIT_USERNAME and FLIT_PASSWORD, the latter of which can be stored as a repository secret to prevent accidentally leaking it. Bonus points for using a PyPI API token instead which allows setting the username to __token__ instead of using login info.
Changes to be made there are limited to removing the current setup.py and instead setting that project configuration in a pyproject.toml. I'd gladly make a PR for it.
The actual commands to run from a workflow file would be limited to python -m pip install flit && python -m flit publish --setup-py
That way my vsfunc repo can add it as a dependency and in general makes the dependent and installation environment much better.
Packaging Python Projects
The text was updated successfully, but these errors were encountered: