Tenacity VS itsdangerous

Hi all. After more then half a year study advanced python and SE principles I would like to develop a library of my liking. I’m aiming for a common decorators library. But after I saw the source code of tenacity (A retry pattern library). I was discouraged. It’s still very complicated to me for now. I can understand a lot of tenacity now. But to code it as beautiful as the auther is tough. Tenacity is not even a big library. My goal is to develop something bigger. I read Learning Python, know many standard library, then two books on SE. A design patterns book for python (broad not deep). And a clean code book (This one is pretty deep). Beyond that I know data structure and algo stuff. I thought I know python at an immediate level now. But seems source code is out of reach. Just wondering how long in python dev before you can develop something like tenacity.

Not sure why you have that impression. The majority of production code I've touched, from networking to distributed systems, implement retry logic. While many have in-house code, developed before retry libraries became available or working within environments unable to pull much external code, the majority of newer code I hear about uses [Tenacity](https://github.com/jd/tenacity).

You're probably looking for something like this: https://github.com/jd/tenacity

Several retry libraries exist. For example, tenacity.

This major release of Flask is accompanied by major releases of Werkzeug, Jinja2, click, and itsdangerous which we'd also welcome and appreciate testing (their pre releases are installed with the Flask pre release).