5 ms·

Or use https://pydoit.org https://pydoit.org and a virtualenv and be happy.

by BiteCode_dev 3y ago

darkteflon 3y ago
Looks like it’s pretty much abandoned: > doit is under active development. Version 0.36.0 released on 2022-04.
- BiteCode_dev 3y ago
  It works great, it's stable, never found a bug for years and it's compatible with the next python release candidates. For the immense convenience it brings, the risk is very low. I'm guessing it could stay that way for 10 years and still be perfectly usable.
- manfre 3y ago
  Below what you quoted > doit core features are quite stable. If there is no recent development, it does NOT mean the project is not being maintained... The project has 100% unit-test code coverage.
  - darkteflon 3y ago
    Okay, but support stops at Python 3.10. I have nothing against the tool - it looks interesting. But isn’t support of current versions of Python table stakes for a tool like this? How am I, as a potential user of this tool, supposed to interpret the lack of 3.11 support and a last release dated end of last year?
    - manfre 3y ago
      After the chaos of Python 2to3, backwards Python's backwards compatibility has been amazing. The tool is created for developers and claims 100% code coverage. Determining if it works with any specific version of Python would be a trivial exercise of clone the repo, make an venv, and run the tests. This is something that a dev should do when evaluating a new dependency even when it claims to support the version relevant to you. Sadly, many do not.
- jselysianeagle 3y ago
  The Github repo shows some commits being made as recently as 4 months ago: https://github.com/pydoit/doit https://github.com/pydoit/doit
polyrand 3y ago
Hi! Author here. I've looked into pydoit multiple times and I would love to try it. There are a few reasons that make me go back to make (no pun intended!). * It comes pre-installed on most UNIX operating systems. Yes, macOS ships an older version, but it works in most cases. This makes bootstrapping projects easier. * I like how simple it's to get started with a Makefile when you just need a few tasks. Although I admit, big Makefiles can become hard to maintain. I've recently experimented with using Makefiles as an ETL orchestrator, and it's becoming quite messy. I believe pydoit is the perfect replacement candidate. I just haven't had time to try it. Edit: Another thing I like about Makefiles is that you can keep the "hackiness" of shell scripts, manipulate the environment [0], etc. I guess you can do the same with other tools, but I find it easier to reason about those useful "hacks" in Makefiles. [0]: https://ricardoanderegg.com/posts/makefile-python-project-tricks/#injecting-paths-into-pythonpath https://ricardoanderegg.com/posts/makefile-python-project-tr...

Or use https://pydoit.org https://pydoit.org and a virtualenv and be happy.

darkteflon 3y ago

Looks like it’s pretty much abandoned: > doit is under active development. Version 0.36.0 released on 2022-04.

BiteCode_dev 3y ago
It works great, it's stable, never found a bug for years and it's compatible with the next python release candidates. For the immense convenience it brings, the risk is very low. I'm guessing it could stay that way for 10 years and still be perfectly usable.
manfre 3y ago
Below what you quoted > doit core features are quite stable. If there is no recent development, it does NOT mean the project is not being maintained... The project has 100% unit-test code coverage.
- darkteflon 3y ago
  Okay, but support stops at Python 3.10. I have nothing against the tool - it looks interesting. But isn’t support of current versions of Python table stakes for a tool like this? How am I, as a potential user of this tool, supposed to interpret the lack of 3.11 support and a last release dated end of last year?
  - manfre 3y ago
    After the chaos of Python 2to3, backwards Python's backwards compatibility has been amazing. The tool is created for developers and claims 100% code coverage. Determining if it works with any specific version of Python would be a trivial exercise of clone the repo, make an venv, and run the tests. This is something that a dev should do when evaluating a new dependency even when it claims to support the version relevant to you. Sadly, many do not.
jselysianeagle 3y ago
The Github repo shows some commits being made as recently as 4 months ago: https://github.com/pydoit/doit https://github.com/pydoit/doit

polyrand 3y ago

Hi! Author here. I've looked into pydoit multiple times and I would love to try it. There are a few reasons that make me go back to make (no pun intended!). * It comes pre-installed on most UNIX operating systems. Yes, macOS ships an older version, but it works in most cases. This makes bootstrapping projects easier. * I like how simple it's to get started with a Makefile when you just need a few tasks. Although I admit, big Makefiles can become hard to maintain. I've recently experimented with using Makefiles as an ETL orchestrator, and it's becoming quite messy. I believe pydoit is the perfect replacement candidate. I just haven't had time to try it. Edit: Another thing I like about Makefiles is that you can keep the "hackiness" of shell scripts, manipulate the environment [0], etc. I guess you can do the same with other tools, but I find it easier to reason about those useful "hacks" in Makefiles. [0]: https://ricardoanderegg.com/posts/makefile-python-project-tricks/#injecting-paths-into-pythonpath https://ricardoanderegg.com/posts/makefile-python-project-tr...