I’ve updated python-intercom recently with the following:

• added support for tagging
• fix bug that prevented installing into a clean environment – thanks vrachil
• PEP8 formatting
• fix to a doctest to pass with current Intercom dummy API.

See PyPi for the 0.2.8 release and Read the Docs for the latest documentation.

Say you have a small script like the following:

import sys
from iron_worker import IronWorker
from iron_worker import Task

worker = IronWorker()
task = Task(
    code_name="HelloWorld", 
    scheduled=True, 
    run_every=sys.argv[1])

response = worker.queue(task)
print response

If you want to schedule the job to run every minute you could call python schedule.py 60. This will unfortunately return an HTTP 400 response.

The reason is that the run_every parameter is being passed as a string. A simple fix is to convert to an int:

task = Task(
    ...
    run_every=int(sys.argv[1]))

django-methodview has been updated with support for (what I consider to be) invalid media-ranges (e.g. just *).

Yes the documentation is *cough* lacking, and I will remedy that in the near future.

See PyPi for the 0.1.2 release.

Cheating is only a problem if your product or service is expensive to deliver; after all, cheaters may be evangelists and future customers.

Steven Dupree on flavors of freemium.

Wise words, as often the guards put in place to prevent cheating are more expensive than the cheating itself.

In light of recent events at PyCon, there has been plenty of discussion about inappropriate conduct. Due to the numerous tangents this discussion has taken, I think it’s important to contemplate why PyCon has a code of conduct.

The first draft of Django’s Code of Conduct hits the nail on the head for me:

Maintaining a code of conduct forces us to consider and articulate what kind of community we want to be, and serves as a constant reminder to put our best foot forward. But most importantly, it serves as a signpost to people looking to join our community that we feel these values are important.