7 ms·
I looked at pyinvoke before I started jeeves. Roughly, as much as I can recall, there were a few reservations: - no type hints for docs & validation, I wanted
by yeti-sh 3y ago
I looked at pyinvoke before I started jeeves. Roughly, as much as I can recall, there were a few reservations:
- no type hints for docs & validation, I wanted them
- Makefile in its basic form is very concise and doesn't require a @task decorator, I didn't want it either
I didn't need dependency graph much.
- mypalmike 3y agoThe whole purpose of make is the dependency graph.
- creshal 3y ago> I didn't need dependency graph much. So you made a Make alternative that isn't a Make alternative because you never needed Make in the first place?
- yeti-sh 3y agoThere are a lot of projects, both commercial and OSS, which have a Makefile for linting, version releases, etc, — and never use its dependency graph feature; or, their usage is so superficial that implementing it, say, - via direct function calls in Python code, - or using Typer callback functions …is easy. There are potential approaches worth exploring (annotations, decorators, …). I might come up with a list of options with syntax examples and ask for community's thoughts about it, — but at this point jeeves, as an MVP, is already useful for me and a few people I work with, and that motivated me to share it with the community.