I got frustrated with having to set up a proper python project with pyproject.toml or setup.py any time I wanted to have some python code importable for my local scripts/misc stuff.
When I have an idea for a python library, I want to be able to try it right away and test it out in my own script writing before committing to setting up packaging.
I've created `nopkg` to ease this pain by allowing any module (.py file or folder of multiple .py files) to be made importable without a full pip install and packaging setup.
`nopkg install mymodule.py`
This enables quick iteration and re-use of custom utilities, as well as more easily sharing modules within small teams.
blakeasm•3h ago
I got frustrated with having to set up a proper python project with pyproject.toml or setup.py any time I wanted to have some python code importable for my local scripts/misc stuff.
When I have an idea for a python library, I want to be able to try it right away and test it out in my own script writing before committing to setting up packaging.
I've created `nopkg` to ease this pain by allowing any module (.py file or folder of multiple .py files) to be made importable without a full pip install and packaging setup.
`nopkg install mymodule.py`
This enables quick iteration and re-use of custom utilities, as well as more easily sharing modules within small teams.
https://github.com/BlakeASmith/nopkg
Please create an issue on the github for any feature requests or feedback! I hope others will find this useful as I have