contrib packages

[wearpants]

Figure out a nice way to package & distribute extensions. We'd like to keep the core only dependent on stdlib. There are a number of useful extensions, mainly different output backends.

Should these all be packaged in a twiggy-contrib or individual packages or what? Where do they live in version control (separate repos or all together)? What namespace do they live in, and how (__package__)?

Check out how Sphinx handles this

[wearpants]

See what else can come from twiggy-goodies

[wearpants]

So the standard way to do this in 2017 is to include all your code in the core package, and specify subsets of dependencies in setup.py. Something like:

pip install twiggy[django]  # pulls in things need for django support
pip install twiggy[twisted]  # pulls in twisted for integration
pip install twiggy[logstash]  # libraries need for LogstashOutput
etc.