These instructions are for sprinters who want to create an open-source Python library.
A great way to contribute to Python is by taking code that you normally copy-paste over and over and packaging it up for the Python Package Index.
TODO screenshot of PyPI
Do you have a script, function, or even a snippet of Python code you copy from project to project? Rather than copying this little bit of Python code, have you ever considered just releasing your code on the Python Package Index (PyPI)? That way you can add tests, documentation, and even get some help on your code. Sounds wonderful, right?
The downside of releasing something on PyPI is that it's not easy. There are a lot of finicky boilerplate files that go into a Python package. While pretty well documented, it's not easy and even the best Python coders often copy/paste the boilerplate code from one project to another. They do this because trying to work through finicky boilerplate simply isn't as productive as creating new packages from existing snippets of code.
This sprint is the an answer to learning how to quickly overcome getting around finicky boilerplate. It will introduce you to a number of useful concepts and a wonderful tool called cookiecutter.
Info "Boilerplate" refers to the starter code that every project begins with.
If you're comfortable writing simple Python scripts or programs, you should be fine.
Knowledge of Python past the "Hello World" basics is recommended. If you've never done a Python tutorial before, you should probably do one and practice writing Python scripts before joining this sprint.
We assume the following of those using this book:
virtualenvwrapperis nice, but not mandatory.
pipto check if your Python package installs locally.
Are you ready to package up some code? Learn some new things? Great! Let's get started.