tomchristie

6 ms·

1.
Python async frameworks – Beyond developer tribalism(encode.io)
6 points by tomchristie 6y ago|0 comments
2.
by tomchristie 7y ago
We don’t have any third party packages for that authentication style yet, but we do have an API for supporting custom auth flows... https://www.python-httpx.org/advanced/#customizing-authentic... If you’re interested i
3.
Httpx: A next-generation HTTP client for Python(python-httpx.org)
463 points by tomchristie 7y ago|115 comments
4.
by tomchristie 7y ago
Yo. Two points here. * You can absolutely stay within structured concurrency constraints using ASGI. * The ASGI spec doesn’t have anything to do with asyncio. It’s purely an async/await interface - You can build against it just fine
5.
by tomchristie 7y ago
That's really lovely, thanks for sharing.
6.
by tomchristie 7y ago
HTTP/3 is slated as roughly HTTP/2 over QUIC but with some differences as a result . https://tools.ietf.org/html/draft-ietf-quic-http-20#appendix... I was dissapointed that the article didn't get into
7.
by tomchristie 7y ago
Good call, given that it's not enabled in modern browsers, and is unreliably supported in proxies and servers. It's for the best that it becomes widely treated as a non-feature of HTTP/1.1.
8.
by tomchristie 7y ago
There's a pretty good reason there's a lot of folks building new frameworks for Python in this space right now: async. Unlike WSGI frameworks we're now able to support WebSockets, lightweight backgrounds tasks, super-high-thr
9.
by tomchristie 7y ago
Python is a hugely productive language. That's the benefit. We're building out an async ecosystem here that makes it way more performance-competitive with Node and Go. For a lot of folks it's going to hit a sweet spot of de
10.
by tomchristie 7y ago
Just wanted to second @tiangolo's "Thanks for paving the way with Hug" - Absolutely yup! It's a lovely bit of interface design - definitely had a really positive impact on the space.
11.
by tomchristie 8y ago
Authorship is always both an individual and a collective act of creativity. We've millenia of shared culture poured into us. Similarly the interplay between the feminine and the masculine voice: Each can only exists in contrast to the
12.
by tomchristie 8y ago
There are 3 ASGI servers right now. Daphne, Uvicorn, Hypercorn. For production deployments you’ll either want to run them with a supervisor process like supervisors/circus/etc. Or use gunicorn (uvicorn includes a gunicorn worker c
13.
Show HN: Starlette – An asyncio Web framework for Python(starlette.io)
8 points by tomchristie 8y ago|2 comments
14.
by tomchristie 8y ago
Yo. Yeah my (bit of) involvement is mostly around wanting to help guide the new ASGI ecosystem. For example, I'd like to see Python's async frameworks building on ASGI middleware rather than all re-writing their own middleware API
15.
Hello, ASGI(encode.io)
3 points by tomchristie 8y ago|0 comments
16.
by tomchristie 8y ago
It’s okay-ish. You do need to be careful about what falsey values `x` might be tho, as it could introduce edge-case bugs. Using `x = [] if x is None else x` is more precise.
17.
by tomchristie 8y ago
> For me this is a simple philosophical question. It really shouldn't be. It's a pragmatic question, based on what the likely outcomes and benefits or harms would be for deregulation. > second of all it is a maturing experie
18.
by tomchristie 8y ago
Hell yes - it's an incredibly productive language, and the Web frameworks for it (Flask & Django in particular) are really nicely mature. For fast Web App development it's a superb language choice. Not so good if you wanted to
19.
by tomchristie 8y ago
I think TechEmpower are doing a great job on these generally, but the plaintext benchmark is problematic because they allow pipelining. (Which isn’t enabled in browsers, isn’t typically used in request libraries and tools, and has generally
20.
by tomchristie 8y ago
Nope, they run a warm up stage.
21.
by tomchristie 8y ago
> It's threaded vs async/await Fair enough, sure. > lack of backpressure You’ll get new calls into the application on new requests, yes. Request bodies are pulled tho. You can perfectly well ensure that server implementation
22.
by tomchristie 8y ago
Nope, but probably going to be working towards a library similar to that/werkzeug. Request & Response objects, plus some standard middleware.
23.
by tomchristie 8y ago
One thing I've never been able to reconcile is Mike Bayer's article there, set against Yury Selivanov's reported results for `asyncpg`, which at least as they're presented do indicate a significant difference in thro
24.
by tomchristie 8y ago
Neat, good to see more `asyncio` frameworks coming along. Python's going to have a bit of an awkward time with two completely different sets of ecosystem for threaded vs. asyncio approaches, but it's necessary progress. One thing
25.
by tomchristie 9y ago
> a meaningful number of developers are openly questioning the web platform. And then going back to building their products. On GitHub. Oh, wait.
26.
API Star: A smart Web API framework, designed for Python 3(github.com)
1 points by tomchristie 9y ago|0 comments
27.
by tomchristie 9y ago
I just had a quick scan over the licenses of other projects used for server side projects. Projects using BSD/MIT include Node, Go, Rails, Django, and Flask. I'm happy with the choice.
28.
by tomchristie 9y ago
One thing to clarify here. Swagger/OpenAPI use JSON Schema in order to describe parameters and response structures. The rest of the schema work will start to fall into place pretty quickly now that we've got the groundwork done.
29.
by tomchristie 10y ago
To be precise I'd call it a "dynamic API client". The codebase doesn't change, you read the schema and corresponding actions become available on the client. There are also "autogenerated API clients", where the
30.
Django REST framework 3.6 released(django-rest-framework.org)
90 points by tomchristie 10y ago|8 comments

More ›