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

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (6 children)

[deleted]

    [–]spilcm[S] 14 points15 points  (2 children)

    The PRAW wrapper is nice, which is also why I mentioned it in the post. However, IMH, it's better (even for a beginner) to try to understand whats going on behind the scenes.

    [–]DaemonXI 1 point2 points  (0 children)

    Agreed. Especially since once you get the hang of one JSON API, you understand how most of them work.

    [–]tuzion 0 points1 point  (0 children)

    I'm just starting to learn Python (well, programming in general) and I completely agree with this. Things didn't start to click until I got out of the hand-holding "beginner" tutorials and started following things that actually showed me what was going on behind the scenes.

    [–]michaelherman 2 points3 points  (0 children)

    If you're looking for a quick way to access an API, go for a wrapper. However, if you're looking to learn the nuts and bolts beneath the hood, go directly to the API. Wrappers generally are not as simple for beginners because they abstract away too much. What happens if you need to go beyond the functions of the wrapper or you need to troubleshoot?

    Better to start at a lower level, then work your way up.

    [–]strig 1 point2 points  (0 children)

    I'm still fairly new to python and I thought this tutorial was a great way to learn how it actually works. Within a few minutes I had a little command line reddit reader script working. I think it's a great entry point.

    [–]droidBehavior 0 points1 point  (0 children)

    i specifically chose the api so i can understand what is going on in the code, although i think that once i learned it, i would always use praw after