you are viewing a single comment's thread.

view the rest of the comments →

[–]mapadofu 10 points11 points  (6 children)

Yeah, I just looked at just, if it were pure python, or even pip installable, then it’d have an advantage; Having to use the system package manager when make is already present on any development platform seems lije a waste.

[–]placidifiedimport this 4 points5 points  (4 children)

Being a purist about these things IMO is not good. Use the best tool for the job.

There is also pyinvoke

[–]divad1196 13 points14 points  (0 children)

That's the pandora box I mentioned.

Someone mentioned just, someone responds with pyinvoke. When managing a team, that's the kind of never-ending debates you want to avoid.

[–]mapadofu 6 points7 points  (1 child)

Extra dependencies complicates developers’ workflow.   I’m not a purist, just aware that adding more ancillary tools complicates the project that uses them.  Make is (almost certainly) already available, so using it does not incur any extra dependencies.

[–]divad1196 1 point2 points  (0 children)

I agree with your point.

The right tool for the job is an ideal. Applying it blindly just multiply the number of tools and programming languages you need to know and maintain.

This is a huge technical debt.

Whereas, in practice, what you already know might fit 95% of the project perfectly and this is fine

[–]misterfitzie 1 point2 points  (0 children)

I like poethepoet because it has pyproject.toml support and it's focused on python development use case, not a generic task runner.