Deal VS Pyrsistent

I started using a design by contract library for a Python project this year and it made my code safer and easier to use.

Have you used Design by Contract in Python projects before? I know that it isn't a first class feature of the language but I see some libraries out there (this one seems potentially promising). Just wondering what the pros and cons are when it comes to gluing DBC onto Python and if anyone can give a yea or nay to it.

deal is a library for Design-by-Contract.

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