Skip to main content

PyCon: Python for Data Lovers: Explore It, Analyze It, Map It

See the website.

I missed the beginning of this talk, and since I'm not a data lover, I'm afraid my notes may not do it justice.

There is lots of interesting, "open data."

There is a lot of data that is released by cities.

She's a geographer and obviously a real data lover. She gets excited about all this data.

csvkit is an amazing set of utilities for working with CSV. It replaces the csv module.

"Social network analysis is focused on uncovering the patterning of people's interactions."

They used QGIS.

She relies heavily on Google Refine.

PySAL is really great for spatial analysis.

She recommended "Social Network Analysis for Startups" from O'Reilly. Her advisor wrote it.


Anonymous said…
Python (or at least, pypy) is a really nice tool for processing data.

Unfortunately, with the GIL, its performance is abysmal, especially on large machines (aka recent desktops) with 8+ cores.

Python really needs to get with the times. I've had to abandon it for now, in favor of D. Maybe someday I'll come back to PyPy, if it ever catches up, but I think the damage is already done.
jjinux said…
The correct way to handle I/O bound processing in Python is gevent, which is not limited by the GIL. The correct way to handle CPU bound concurrency in Python is via using multiple processes.

In Guido's keynote, he said, "OS level threads are meant for parallel IO, not for parallel computation." Use separate processes for each core. One team was using Python on a machine with 64,000 cores.

D is a nice language, but I don't believe it's fully open source. Go is probably better. Neither one has the breadth of third-party libraries that Python has.

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

JavaScript: Porting from react-css-modules to babel-plugin-react-css-modules (with Less)

I recently found a bug in react-css-modules that prevented me from upgrading react-mobx which prevented us from upgrading to React 16. Then, I found out that react-css-modules is "no longer actively maintained". Hence, whether I wanted to or not, I was kind of forced into moving from react-css-modules to babel-plugin-react-css-modules. Doing the port is mostly straightforward. Once I switched libraries, the rest of the port was basically:
Get ESLint to pass now that react-css-modules is no longer available.Get babel-plugin-react-css-modules working with Less.Get my Karma tests to at least build.Get the Karma tests to pass.Test things thoroughly.Fight off merge conflicts from the rest of engineering every 10 minutes ;) There were a few things that resulted in difficult code changes. That's what the rest of this blog post is about. I don't think you can fix all of these things ahead of time. Just read through them and keep them in mind as you follow the approach above.…