returns VS Pyrsistent

returns – Make your functions return something meaningful, typed, and safe

you haven’t heard of https://github.com/dry-python/returns

returns from the DRY python group appears to offer similar functionality.

Not to diminish this at all, but https://github.com/dry-python/returns also exists. The scope is wider, but the look and feel of the types feels very similar.

https://github.com/dry-python/returns#maybe-container

You can decide for yourself what is more readable: all these lambdas or the `None and f()` code.

There is a Python library called returns (https://github.com/dry-python/returns) that allows you to write functional code in Python

There are python libraries that implement Clojure style functional data types. Have you tried pyrsistent - https://github.com/tobgu/pyrsistent

Hissp is really interesting. Read through the docs and you'll understand Python more deeply. It works well with Toolz and Pyrsistent.

This is normal for some functional languages, since by definition they should prohibit assignment and hence mutation. But you can also achieve a similar (not the same) effect in python, using libraries like pyrsistent (https://github.com/tobgu/pyrsistent/)

It still is, and Cython is great for accelerating critical Python code.

A C extension is far preferable when you want to code in C, either to write a new data type[1], or write a Python frontend to a C library[2] that is too complex to be well supported by simple FFI.

I think people use Cython more internally when they value the maintainability of "mostly Python" over the fact that it's slower than what native C would get them.

[1]: https://github.com/tobgu/pyrsistent

[2]: https://github.com/libgit2/pygit2

There's Pyrsistent[1], which provides persistent data structures.

[1] https://github.com/tobgu/pyrsistent