Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibility of pushing mvsfunc to PyPI (pip)? #5

Open
rlaphoenix opened this issue Jan 2, 2020 · 1 comment
Open

Possibility of pushing mvsfunc to PyPI (pip)? #5

rlaphoenix opened this issue Jan 2, 2020 · 1 comment

Comments

@rlaphoenix
Copy link

rlaphoenix commented Jan 2, 2020

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

@RivenSkaye
Copy link

RivenSkaye commented Jul 25, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants