3 ms·
Suggestion: take the time to package this up for PyPI as something people can install using "pip install" (or "pipx install"). This is hard the first time you
by simonw 5y ago
Suggestion: take the time to package this up for PyPI as something people can install using "pip install" (or "pipx install").
This is hard the first time you do it, but worth learning because it's a really great way to distribute your Python software.
I'm giving a talk about how to do this at PyGotham next month, but the notes from that talk are already available and may be useful to you: https://github.com/simonw/pygotham-packaging https://github.com/simonw/pygotham-packaging
You may also find this cookiecutter template that I use to build and package Python CLI apps helpful: https://github.com/simonw/click-app https://github.com/simonw/click-app
- dwohnitmok 5y agoIs there a way to distribute proprietary software with PyPI? Based on the license text it appears the author wishes to keep it proprietary (maybe source-available, but not open source).
- uranusjr 5y agoI suppose you actually mean close source? Because it’s trivial to distribute proprietary code on PyPI: Just say that in your license. There is no true “close source” for pure Python programs, but if obfuscation is close enough, you can choose to only deploy wheels containing pre-compiled pyc files. This is good enough for most situations.