Toolz VS taskipy

My favourite lib would probably be toolz, it's just so elegant and fun to use. But it's more functional approach is not always the best fit for the time, so in practice I mostly use it in research, prototyping, console and notebooks.

I am not new to Python but only used it to write scripts. Should I start a Python book and then a PySpark book or go directly to PySpark? When reading the legacy code, I found there are usages like GitHub - pytoolz/toolz: A functional standard library for Python. I never heard of.

toolz is wildly useful https://github.com/pytoolz/toolz

Maybe the toolz[0] family would cover your use cases? There is also a Cython implementation if you need better performance.

[0] https://github.com/pytoolz/toolz/

You'll probably enjoy toolz.

pdbpp: Improved pdb boltons: assorted python addtions twisted: event driven networking framework sorcery: Dark magic in python, things know where+how they are being called, helps reducing boilerplate sh: Better alternative for subprocess module, much more pythonic taskipy: npm run scipt_name like functionality snoop: pdb lite, record+replay function steps birdseye: graphical debugger remote-pdb: easy pdb from inside containers typer: wrapper around click for simpler code for CLIs arrow: Always TZ aware datetimes, plus more features more-itertools: more functions for iterators pydantic: data validation + dataclasses loguru: better logging notifiers: sending notifications from python

Taskipy

taskipy – complementary task runner for python

I always use Taskipy https://github.com/illBeRoy/taskipy to run tasks in my applications, works really well with Poetry so when I am running my dev Flask/FastAPI server and Celery or running my tests or format my code it's all there.

```

In legacy (don't break anything) mode, there's still no reason to not switch. I export `requirements.txt` with poetry just for pip legacy reasons and it works great. If I just update some scripts, I could avoid it. It's running all the time in CI, it's exercised quite a bit.

What's wrong with just using pip and requirements.txt? There's no dev section. In addition, bumping deps is not the same. I have [a blog post](https://squarism.com/2021/09/10/sciencing-out-updates/) explaining semver updates to a python dev.

_my strong assertion:_ Python and Go missed it from the start. That's why it is so confusing. There's no other choice in Rust but Cargo. Rust devs are never confused on how to add a package, semver it. The answer is always Cargo. It's in the tutorial. It's in the book. It's in the culture.

I think I've heard that pip might support the pyproject spec, poetry already does. If you want scripts like npm, you can have that too with [taskipy](https://github.com/illBeRoy/taskipy). You don't have to.

taskipy