1,081 reputation
78
bio website
location St. Andrews, United Kingdom
age 17
visits member for 4 years, 7 months
seen Nov 3 at 20:01

Maths student at St Andrews University, Scotland. Hobbyist programmer. I dabble in a few languages; mainly Python and C at the minute.


Jun
10
comment Py-StackExchange: An API wrapper for Python
Ahem. Revisited this, doing browser testing. The reason from_date and to_date work is that they are ignored. Compare the total field on api.stackoverflow.com/1.1/… to api.stackoverflow.com/1.1/…. Either way, you can pass in a float if you want now; in the latest revision it'll be appropriately converted behind-the-scenes.
Jun
10
revised Py-StackExchange: An API wrapper for Python
added 208 characters in body
Jun
9
comment Py-StackExchange: An API wrapper for Python
Unfortunately, about all you can do is pass pagesize=100 to Site.questions. You can then use the methods on the returned resultset to advance through the pages. You won't be able to get anything bigger than 100 at a time, though. There are a couple of other options: you could try and export results from data.stackexchange.com, but those will probably be size-limited too. 'Worst case', you could download the data dump, but it's rather large (multi-gigabyte range) and hard to deal with.
May
25
comment Py-StackExchange: An API wrapper for Python
I'll double-check this, but unaccepted_questions is probably one of the fields that is not fetched automatically; instead use ii.get_user().unaccepted_questions.fetch().count. I know this is a little clunky, but otherwise it would need to pull in tonnes of data each request.
May
23
awarded  Yearling
May
18
comment Py-StackExchange: An API wrapper for Python
@LarsH: That's a good idea; it'll also encourage me to keep as close to 100% coverage as is humanly possible!
May
18
comment Py-StackExchange: An API wrapper for Python
Note to future readers: a nicer API is supported in v1.1: site.questions.by_user(uid).
May
18
comment Py-StackExchange: An API wrapper for Python
Doing some testing... strange: with from_date=aWhileAgo and to_date=currentDate it works, as it does with fromdate=int(aWhileAgo) and todate. But using a float as fromdate (as aWhileAgo was), which is formatted with a trailing .0 fails with error 500. So both work with integers; this might be an API inconsistency.
May
18
comment Py-StackExchange: An API wrapper for Python
While I'm here, I'll try putting in some more descriptive exceptions, too.
May
18
revised Py-StackExchange: An API wrapper for Python
added 134 characters in body
May
18
comment Py-StackExchange: An API wrapper for Python
@LarsH: That, and the wiki (also on Github). Will clarify.
May
18
comment Py-StackExchange: An API wrapper for Python
Hello; sorry for the delay, glad you solved your problem. To answer your first question, you can turn on debug printing of URLs by setting stackexchange.web.WebRequestManager.debug = True. I agree that the documentation in that area is lacking; a wiki page is coming up. I'll look into that inconsistency; it seems quite pointless... I apologise on behalf of my younger self.
May
4
comment Py-StackExchange: An API wrapper for Python
Sorry for the delay - OpenID/hosting problems... Anyway, doing some testing, I noticed that Django view parameters are Unicode strings. I hadn't thought to have handled Unicode explicitly in the library, and it turned out that the urllib module encodes it as UTF-16 by default, which the API (understandably) doesn't like. I've changed it to UTF-8, which now works under Django for me. Summary: update to the latest version in the Git repo. (Or, I can push a new release of the egg out if necessary.)
May
4
comment Py-StackExchange: An API wrapper for Python
Not as far as I know, unless you use client-side JavaScript or something like that to fetch the result. You'll probably be fine with a single key, with an increased quota if necessary. The SO team are very approachable ;).
May
2
awarded  Notable Question
Apr
30
comment Py-StackExchange: An API wrapper for Python
You could well hit the limit if you get lots of hits. See stackapps.com/questions/67/how-api-keys-work for the official line. If your quota is increased, you won't need to change any code except to make sure you're using your API key.
Apr
5
comment Py-StackExchange: An API wrapper for Python
@Sridhar Ratnakumar: Thanks for the edit there; you beat me to it! :)
Mar
6
revised Py-StackExchange: An API wrapper for Python
deleted 5 characters in body
Feb
23
comment Py-StackExchange: An API wrapper for Python
Updated version on Github, and the egg should work now.
Feb
23
comment Py-StackExchange: An API wrapper for Python
Aha. I should probably rename build.sh to release.sh - it's the script I use for publishing new releases to PyPI. I'll write a README or something too... anyway, it should just work, from Github, out-of-the-box without running the script. If it doesn't, let me know! :)