Sometimes I just want to execute a python callback and pass args/kwargs on the CLI, and not have to define any custom CLI entry point of any sort, nor change any code, typically when automating stuff, cli2 unfrustrates me (pun intended):

cli2 yourmodule.yourcallback somearg somekwarg=foo

Sometimes I just want to define a new command and expose all callables in a module and I can’t just do it with a one-liner. cli2 unfrustrates me again:

Zulip Advertisement

https://repl.it/@jpic/crudlfap

https://playlabs.readthedocs.io/en/latest/

Playlabs documentation is now available online ! Playlabs provides a convenient wrapper for the ansible-playbook command and provides a set of ansible roles made to work together, and to orchestrate containers as much as possible and let only network level provisioning happen on hosts themselves, and combines straigthforward ansible patterns to install a docker orchestrated paas infra to prototype products for development to small-size production. Pre-beta state: works for me, but parts are being rewriten independently until it’s clean enough and declared stable, documentation is still in progress and so are tests. Read more at playlabs.rtfd.io

https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/issue_workflow.md

Excellent read about GitLab’s internal issue workflow, safe to assume they automated as much as possible in GitLab itself.

http://pyparis.org/talks.html#core-python

https://github.com/owais/django-webpack-loader/pull/182

django-webpack-loader code splitting support by @alihazemfarouk, that has a sister pull request.

https://asciinema.org/a/Jn3LB6TO7vWcf2xhZnGmwLJ86

For hacker only: Full feature CLI CRUD+ for Django vidéo demo.

https://developers.redhat.com/articles/podman-next-generation-linux-container-tools/

Why you should pay a hacker 10k/year to maintain your GitLab-CI/Drone-CI/etc server on baremetal With LOVE