How to Run Python in Production

&quot;Consider using an unstable package manager&quot; is a really really rough start.<p>additional: &quot;However, writing your own code that involves async functions&quot;, your code <i>does</i> use async functions, its just monkey patched into your program because you used green threads instead.

Multithreading is not a prerequisite for async in Python. The default task executor runs in a single thread. So using async APIs should be safe as long as you stick to the single-threaded executor.

It sounds like the author makes a blanket claim to avoid asynchronous functions, even when using an inherently asynchronous web framework (FastAPI), which would negate any FastAPI asynchronous concurrency gains.

On the &quot;formatters&quot; and &quot;linters&quot; front, there is no need to use anything else than ruff, since it incorporates the functionality of all the other tools mentioned.

Perhaps better titled as something like “my personal preferences for how I like to run python in production”.<p>Presenting these opinions as truths will get the hackles up of those who have a different opinion.

But you don&#x27;t recommend it? (33 points, 38 comments) <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43297671">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43297671</a>

So first off, don’t use Python in prod. Second off, don’t use async because of complexities in multi-threading?<p>A lot of the world runs just find on Python (see Django), async is mature and stable.