News for hackers. Stuff that matters.
Re:Makefiles – Best Practices by igor47 on Friday February 01, 2019 @12:10PM (#19055996)
I've been using invoke [1] which has allowed me to give my projects nice UIs while remaining in the primary language. If I were working on Ruby I would stick with Rake, even though I think invoke is better.

[1] http://www.pyinvoke.org/

Re:Makefiles – Best Practices by tedmiston on Friday February 01, 2019 @02:13PM (#19057416)
I really like Invoke / Fabric for Python projects, though it feels weird to use in non-Python projects when it comes to dependencies. [Now I have to explain to non-Python people things like virtual envs, pipenv vs pip vs pipsi, pyenv, etc.]

Just curious if you install Invoke individually for each project or keep one global install?

I suppose I could always git exclude the tasks.py Invoke files.

Re:Makefiles – Best Practices by learned on Friday February 01, 2019 @06:29PM (#19059799)
I usually keep Invoke globally installed that way I can use it for setting up and interacting with pipenvs externally. Most of my calls beside the initial setup make use of 'pipenv run <command>' that way I never actually have to navigate inside of the virtualenv for most cases.
Re:Makefiles – Best Practices by learned on Friday February 01, 2019 @01:17PM (#19056775)
I'll second invoke. I use it for all of my python projects now and I love working with it. It makes it very clean to manage more complex tasks that have a lot of conditionals involved.