sobolevn

<3

I also have a very warm relationship with Django. I used it for my first ever Python project back in 2010. And it made me to ditch Java and come to Python land. Great memories!

That's quite unexpected that Citus is not always ACID. I wonder if there are other PostgreSQL extensions, which are ACID

Hi, author of `returns` here! Thanks a lot for sharing this link.

I would love to highlight several features of `0.14` release we are working on right now:

1. Typed `partial` and `curry` functions: https://returns.readthedocs.io/en/latest/pages/curry.html

2. `Future` and `FutureResult` containers for working with async Python! https://returns.readthedocs.io/en/latest/pages/future.html

3. Typed functional pipelines with very good type inference: https://returns.readthedocs.io/en/latest/pages/pipeline.html

It is going to be released soon, stay tuned!

There's a better solution: use open-source cli tools that do just that!

1. 520 Python checks? Use `wemake-python-styleguide` (wrapper around flake8) that has bigger amount of checks: https://github.com/wemake-services/wemake-python-styleguide There's also `pylint` with a set of awesome checks as well.

2. Type checking? Use `mypy`: it just a single command!

3. Autofixing? Use `black` / `autopep8` / `autoflake` and you can use `pybetter` to have the same ~15 auto-fix rules. But, it is completely free and open-source

I don't like this whole idea of such tools (both technically and ethically):

- Why would anyone want to send all their codebase to 3rd party? We used to call it a security breach back in the days

- On moral side, this (and similar) projects look like thin wrappers around open-source tools but with a monetisation model. How much do these companies contribute back to the original authors of pylint, mypy, flake8? Ones who created and maintained them for years. I will be happy to be wrong here

Thanks, my idea was to state the problem and propose a solution. Hope, that you will find `returns` helpful.