PyCon tutorials, day one


17:00: This afternoon's tutorial was an introduction to statistical modeling. We started off badly when the instructor sent us the preparatory instructions about two hours before the start. It included downloading and installing Anaconda, which is a mother of a download and a mother of an install. The available time was actually less than two hours … Continue reading PyCon tutorials, day one

Python 3


Helping my company migrate everything to Python 3. Righteous! And we'll update everything else, including Django, when we do it. If only an updated Python Essential Reference was available... I'd buy it for every developer. I can't hassle David anymore since I left Twitter. 'Tis a shame. I could send him email and text messages, … Continue reading Python 3

Solinea is looking for a Senior Backend Engineer (Python, Django, Elasticsearch)


This is my second week at Solinea, and I'm loving it! A position just opened up on our development team for a backend developer, and I wanted to share the love. 🙂 The company supports remote employees. Its headquarters is in Berkeley, CA, and I'm in Seattle, and I feel more connected now than, well, … Continue reading Solinea is looking for a Senior Backend Engineer (Python, Django, Elasticsearch)

IP Street is hiring! Senior Developer (Python, Django)


Overview Founded in 2010, IP Street has built the world’s preeminent Intellectual Property(IP) analytics and visualization engine, in conjunction with a nationally recognized IP law firm. Our SaaS product helps corporations and financial analysts quickly and efficiently analyze IP information.  We make IP data easy to get, use, and understand! As with any organization, we’ve continued to evaluate new ways to … Continue reading IP Street is hiring! Senior Developer (Python, Django)

Our Python 3 migration status


IP Street's application runs on Python 2.7. Earlier this week, I evaluated all our Python packages for Python 3 support, as the first step in deciding when to migrate our codebase. Although this was the time I've checked our packages for Python 3 support, I expected Django to be the only one that didn't officially … Continue reading Our Python 3 migration status

IP Street is looking to hire a Senior Developer! (Seattle)


If you know someone who fits the bill, send them this post! ———————————— Title: Senior Developer Reports to: VP Engineering About IP Street Founded in 2009, IP Street develops and markets software to help corporations, law firms, and financial analysts better analyze patent-related information. We make IP data easy to get, use, and understand! Summary … Continue reading IP Street is looking to hire a Senior Developer! (Seattle)

Alternatives to using Celery


I've found some candidates for replacing Celery in my company's product. (My reasons for replacing it are elucidated here, here, and here.) I got these from web trawling, blog comments, and some e-mail. At first blush, none of the candidates have any disqualifying attributes, except for lacking subtasks. Celery is the only Python-friendly asynchronous task … Continue reading Alternatives to using Celery

My requirements for replacing Celery


I'm ready to start looking at candidates to replace Celery in my company's product. (The reasons are elucidated here, here, and here.) Our SaaS product provides data mining and visualization for intellectual property. A 10-second elevator pitch is, it's as though we attached Microsoft Excel's chart wizard to US and international patent offices. ("As though" … Continue reading My requirements for replacing Celery

Breakage when upgrading from Celery 2.5.3 -> 3.0.4


Commenting on my update to my Celery rant, @asksol asked me to post the Pylint results that made me question the claim of backwards compatibility. ("@Asksol asked" — See what I did there? That's alliteration. It's a sign of a quality blog post. Ask for it by name.) Again for the record, @asksol is a … Continue reading Breakage when upgrading from Celery 2.5.3 -> 3.0.4

An update to my Celery rant


An update to my rant on Celery's frequently-changing API: I've decided to stay with Django-celery 2.5.5 and Celery 2.5.3. When I tried using Celery 3.0.4 with my existing code, Pylint threw about 60 warnings, many of which look real and all of which weren't there when I used Celery 2.5.3. "Backwards-compatible" my ass! I shouldn't … Continue reading An update to my Celery rant