network profile
| bio | website | lucasjones.co.uk |
|---|---|---|
| location | Stirling, United Kingdom | |
| age | 16 | |
| visits | member for | 3 years |
| seen | May 11 at 15:23 | |
| stats | profile views | 41 |
I'm a hobbyist C#, Python and Ruby programmer and web developer.
|
Jun 15 |
comment |
Py-StackExchange: An API wrapper for Python @Edan: Darn comment edit time limits. It's actually user_id not userid in the library code. |
|
Jun 15 |
comment |
Py-StackExchange: An API wrapper for Python @Edan: Done now in the latest revision, with the same syntax. fetch_page (but not other overloads right now) can do the same, too. |
|
Jun 15 |
comment |
Py-StackExchange: An API wrapper for Python Finished in latest revision. |
|
Jun 15 |
comment |
Py-StackExchange: An API wrapper for Python @Edan: Not quite, but it should be done soon. |
|
Jun 15 |
comment |
Py-StackExchange: An API wrapper for Python OK, that seems reasonable. And those bonus points should be attainable quite easily! :) |
|
Jun 14 |
comment |
UI Improvements when editing your Application Registration I personally agree with both of those - they seem simple enough. (And rather obvious!) :) |
|
Jun 14 |
comment |
Py-StackExchange: An API wrapper for Python Done in latest revision. site.root_domain and {user|question|answer}.url. Beware that this is hard-coded and relatively hacky! :) |
|
Jun 14 |
comment |
Py-StackExchange: An API wrapper for Python Right. I have an idea how I'd do this! :) |
|
Jun 14 |
comment |
Py-StackExchange: An API wrapper for Python That seems like a good idea on both counts! Will have a look at this. |
|
Jun 13 |
comment |
Py-StackExchange: An API wrapper for Python @Edan: Not in your specific case right now (see the FAQ - link in question - for those that are covered), as I'm not sure how best to implement it. Do you think calling me.answers.fetch(body='true') would be best? |
|
Jun 13 |
comment |
Py-StackExchange: An API wrapper for Python I've also updated the FAQ with this, as it's not documented very clearly. |
|
Jun 13 |
comment |
Py-StackExchange: An API wrapper for Python Ah, sorry. Due to a change in the API (I think - or perhaps me just being stupid and not reading the docs close enough!) question and answer bodies need to be explicitly requested. You can do this through so.be_inclusive(), which you should call before your first request. |
|
Jun 13 |
comment |
Py-StackExchange: An API wrapper for Python Done in latest revision. |
|
Jun 13 |
comment |
Py-StackExchange: An API wrapper for Python Thanks for that! I'll have a look at implementing that today. |
|
Jun 12 |
comment |
Py-StackExchange: An API wrapper for Python In my to-do list now! wiki.github.com/lucjon/Py-StackExchange :) |
|
Jun 12 |
comment |
Py-StackExchange: An API wrapper for Python That is very weird. I have added it to my quick-and-dirty to-do list wiki.github.com/lucjon/Py-StackExchange. |
|
Jun 12 |
comment |
Py-StackExchange: An API wrapper for Python Done in the latest revision. |
|
Jun 12 |
comment |
Stack2Blog - Turning your answers into blogs (For “sale”) I personally would rather the comments weren't there - from the usage scenario you put forward in the question (person blogging own answer/question), they would add little. (IMHO, of course.) |
|
Jun 12 |
comment |
Py-StackExchange: An API wrapper for Python I've added the patch manually (it's only small :D), but I can't figure out how to do it with Git - git apply didn't work. Just for future reference, do you know how I'd do that? |
|
Jun 12 |
comment |
Py-StackExchange: An API wrapper for Python Thanks - I'll add the diff for now, to keep compatibility. I may factor it into the be_inclusive() method later, though. |
