PRAW VS lxml

I'm... not sure I understand the question? PRAW still works just fine for "personal use" of the reddit API.

Thank you for pointing out. So there is no need then for the access token? Only with the refresh token is enough? To be honest I took a look at it but I did not expect that to be under authentication as strictly speaking, the user already made the authentication. Also I took a look at the code at https://github.com/praw-dev/praw/blob/master/praw/reddit.py and I did not get a hint whether was possible to pass it or not. I am just saying this to let you know I tried to search for the answer before asking. Again thank you for the help.

To get the relevant IDs, you can use something like PRAW to query the subreddit for the top 1000 posts for example.

Huge thanks to the contributors to PRAW, which is the Python package that does all the heavy lifting relating to Reddit's API that I need for this script.

However, in practice duplicate items were yielded with these smaller numbers. So I increased the limit briefly to 250 in October 2016, and then increased it finally to 301 in December 2016 in order to resolve https://github.com/praw-dev/praw/issues/673. That issue provides an explanation for how 301 came to be.

Why? You gotta be ready for any status code. Even 777.

lxml

Parsel is a library build to extract data from XML/HTML documents with XPath and CSS selectors support, and could be combined with regular expressions. It's usees lxml parser under the hood by default.

So, now that I no longer work in that industry, and I had some free time, I created a lazy parsing package using lxml instead of the xml parser in the standard library, which can help people who want to have a python only parsing solution.

Seriously, use LXML.

I got curious about this now so I did some tests on my own, and it appears that the XML parser implementation in Python does indeed strip all newline characters from attributes. Whether this is according to XML standard I do not know; I also briefly tried an alternative XML implementation for Python and it behaves the same, so I would assume that this is standard behavior, but I'm not knowledgable enough about XML to say for certain.

I use lxml for the XML parsing and pyodbc as the ODBC library. We have a small team so I just keep it as simple as possible: 1. A cursor yields the XML documents from a SQL query as a stream 2. A generator function parses the XML document and yields the rows (you could parallelize this step) 3. Stream each of the resulting rows to a single CSV file 4. Scoop up the resulting CSV file into the target database (usually with the DB engine's loader; bulk insert isn't so fast over ODBC) It ends up being a straight forward, low-overhead approach.

If that sounds too weird maybe take a look at pycomm3, python also has lxml as well as requests. You could write a script that retrieves the data from the clx using the appropriate pycomm3 driver for cplx and then do xml things with the data using lxml and transmit the data over http using requests.