Improved version of Edgeworth's Python 4chan API Wrapper.
Project description
Python Wrapper for 4chan API. Uses requests, respects if-modified-since headers on updating threads. Caches thread objects. Fun stuff.
You can install this wrapper library straight from PyPi.
This is the Bibliotheca Anonoma StoryCorps’ (BASC) updated fork of py4chan, based on Edgeworth’s outdated original.
4chan Link Structure Update - 4chan has heavily reformed it’s link structure, finally removing the strange folder structure inherited from the Futaba Channel. However, it requires the scripts to be updated.
4chan cdn Link update - To save money on bandwidth. 4chan has changed it’s image/thumbnail/json/css servers to a domain name with fewer characters. However, that requires us to update py-4chan links, and that has not been done yet.
Anorov’s underscore_function_notation - Even I have to say that CamelCase is beginning to suck. However, you will have to rename all your function calls for existing apps, but that’s just a find/replace away.
Renamed files() to images(), and any ``files`` property to ``images`` - 4chan only hosts image files, so the name of this function gets confusing, since it can refer to either images thumbnails. The has_file and file_deleted property retains it’s name, though, since it refers to both thumbs and images.
images() and thumbs() - now return images instead of URLs. The original functions have been renamed to image_urls() and thumb_urls()
Post Class: image_fname and thumbnail_fname property
Actual API Documentation - Real documentation on using the py-4chan library is a must. For some people, it is rocket science.
Sample Usage
import py4chan
b = py4chan.Board('b')
thread = b.get_thread(423491034)
print thread
for file in thread.files():
print file
# In a while...
print "I fetched", thread.update(), "new replies."API Documentation coming soon, but you can figure most of it out from the source. It’s not rocket science.
