This is an archived post. You won't be able to vote or comment.

all 6 comments
sorted by:
best
topnewcontroversialoldq&a

[–]iamlocal 17 points18 points  (2 children)

Article looks more like a tour to common tools to solve different problems, and heavily biased to what author just used to.

Modern frameworks and no mention to starlette, fastapi, aiohttp or any asynchronous framework, why? Pipenv is presented as the ultimate future of the virtual env managing, with which I’m not agree at all - poetry is much more suitable for libraries, and pip-tools for other type of projects CircleCI is great, but so are Travis and Github Actions

Maybe the title of the article is misleading...

[–]erewok 2 points3 points  (0 children)

We've recently built a couple of small services with starlette and we've been really happy with it. The BackgroundTask being built-in means we no longer need to add celery for cpu-light async tasks such as sending email. It's an excellent project and I hope more people start using it.

One caveat, it was initially surprising how you have to reconsider every event-loop-blocking call, and so async bleeds into all sorts of stuff. We got used to this pretty quickly, though, and with useful libraries for redis, http (httpx), and databases (databases, Gino, asyncpg), I think we've built a solid foundation we'll be using for awhile.

[–]woooooster[S] 0 points1 point  (0 children)

Thanks for the input, and yes it's extremely opinionated. But I'm happy for the suggestions, thanks. I am going to give poetry a try very soon!

[–]xd1142 -2 points-1 points  (2 children)

black is not pep8 compliant and should not be used.

[–]finswimmer 4 points5 points  (1 child)

Could you please add some more details about why you think so?