1,061 reputation
78
bio website
location St. Andrews, United Kingdom
age 17
visits member for 4 years, 4 months
seen Sep 1 at 15:09

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


Aug
28
comment Py-StackExchange: An API wrapper for Python
Thanks for bringing this to my attention, I've fixed the problem in the latest revision on the Github repository (github.com/lucjon/Py-StackExchange). Your code should now work if you use the version of the library from there.
Jul
4
comment Py-StackExchange: An API wrapper for Python
Thanks for letting me know about this; however, I've not been able to reproduce it myself. Is there anything unusual about your setup (in particular, are there any proxies between you and Stack Exchange?) which might get in the way? Either way, if changing the 'encoding' is as harmless as it seems to be from my initial look at the documentation, I may well just change it.
Jul
2
comment Py-StackExchange: An API wrapper for Python
Thanks for letting me know about this, it's a 2.x change that slipped through. The field is now called is_accepted; I've pushed a fix to the Github repository.
Jun
26
comment Py-StackExchange: An API wrapper for Python
This is indeed a Python 3 issue; I have fixed this and a few other compatibility problems just now in the latest version of the library available on Github. The master branch targets v2.x of the StackExchange API, as will the latest PyPI version in the near future. If you want to continue using v1.x (e.g. you have an API key registered), the compatibility fixes have been backported to the v1.1 branch on Github.
May
27
comment Py-StackExchange: An API wrapper for Python
Thanks for getting in touch. The demo works for me locally; could I ask you to do the following: (1) ensure that you are using the latest version of the library from the Github repository; (2) if the problem persists, enable debug mode by adding the line stackexchange.web.WebRequestManager.debug = True to the top of your script.
May
3
comment Py-StackExchange: An API wrapper for Python
@Andy: Not currently, but I'm certainly having a look at it.
May
1
comment Py-StackExchange: An API wrapper for Python
@Eric Leichtenschlag: Thanks for letting me know; my apologies for not replying to you at the v2.2 is now the primary API version targeted by the library (the v2.x branch has been merged, etc.).
Feb
3
comment Py-StackExchange: An API wrapper for Python
@Eric Leichtenschlag: While I'm sure I'm overlooking something obvious, I can't find a source for your exact date for a v1.x shutdown. The v2.x branch of the repository has improved somewhat since my last comment here, passing its (small) set of unit tests. The Python API remains almost identical. Certainly if there were such a date it would be a useful motivator; while I can't make any guarantees, I imagine the finishing touches could be put on before then.
Oct
21
comment Py-StackExchange: An API wrapper for Python
@MattDMo: Regrettably, the 2.0 branch is not entirely stable, mainly due to differences in the way filters work, and the coverage is certainly not complete. As you have deduced, there has not been much meaningful effort dedicated to improving it for a significant period of time; I currently have no explicit plans to update it for v2.1. The existing v1.x code remains entirely functional if you don't require any of the new API calls.
Dec
20
comment Py-StackExchange: An API wrapper for Python
This is, unfortunately, correct.
May
11
comment Py-StackExchange: An API wrapper for Python
OK. The behaviour of the iterators changed recently. Site.questions.no_answers, Site.questions.recent_questions and Site.questions.unanswered will go on forever. The pagesize= argument actually tells the API how many items to return on each iteration - it will just keep iterating until it's returned all the pages. I agree this is not the most useful behaviour for this case, and I'm now planning to add a cleaner interface. For now, though, change your loop to for qq in ii(...).items, which will only iterate through the questions on the first page, of size pagesize.
May
7
comment Py-StackExchange: An API wrapper for Python
I have a feeling I may have fixed this bug in the latest version of the code, but that I haven't pushed it to PyPI. I'll try and push the latest code up; in the meantime you can get it straight from the repository at github.com/lucjon/Py-StackExchange.
Apr
12
comment Py-StackExchange: An API wrapper for Python
@systempuntoot: Thanks for the comment; it arrived in my inbox and reminded me I've not finished updating it yet! There is a branch on Github I started a while ago with some basic things working... I'll try and get that finished as soon as I can.
Jan
7
comment Py-StackExchange: An API wrapper for Python
Currently, keyword arguments are effectively passed verbatim to the API (albeit with a bit of processing to make them work in a URL). The best documentation I can offer in that regard are the official API docs. Regarding your second question: unfortunately, the current version of the API (v1.1) and the next planned version (v2.0) are read-only; you won't be able to star questions, although I think v2.0 will provide authentication functionality.
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
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
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.