this post was submitted on 28 Jun 2023
5 points (100.0% liked)
Technology
37705 readers
394 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm getting back into Python for unrelated reasons, and last I was using it, JSON wasn't on my radar yet.
I'm curious about the
.json()
method here, which seems to be exposingposts
et al. for further manipulation without parsing. Is this really as simple as it appears?Yes, it totally is that easy. At first I used an API wrapper library, but then I checked out the source and there is really no need for it since requests already handles basically everything.
.json()
takes the response body of the request and runs it throughjson.decode()
and thus spits out a nice Python dict/list structure.It is absurdly simple and powerful.
I've not used
requests
, but yes their docs make it look like it really is that easy: https://requests.readthedocs.io/en/latest/user/quickstart/Looks like the
.json()
call just returns a dictionary (or maybe a list of dictionaries), which means you can use all of python's normal dictionary methods to find the data you're looking for!Thanks for the link! This looks like an absurdly powerful library for HTTP needs and output manipulation from the perspective of a scraping neophyte.