Skip to main content

PyCon 2013 Posts I want to see

PyCon 2013 will be my third PyCon, and I'm walking into it with a better idea what I'm hoping for than my first two. Here is my shortlist for talk hopes.

  • Python inside Government
    Are any federal, state, or local governments using Python internally? In any important or large ways? Maybe at the national archives or the library of congress? I want to know about these things! Does the IRS crunch my taxes with Python?

  • Python and Big Data
    Working with large datasets fascinates me, probably because I don't get the opportunity to do so. I'd love to see where Python is being used to crunch big datasets. I wonder if gets used in any pipelines in processing results from CERN? Or maybe diagnosing medical tests?
  • Python close to the wire, embedded or working with wire protocols
    Using Python in mobile devices, embedded devices, or implementing binary protocols on the wire that need to work fast and with low latency? These are things people often don't think Python does well, so prove them wrong.
  • Python in movies
    Pixar, Disney, I know you guys are out there! Is python used in stages of the pipeline to make all those 3D movies I take my kids to see?
  • Community-centric talks, please!
    These are personally interesting to me, because I want to build community. I want to learn from more people who are great at it.
If you can give any of these talks, or any talk at all, submit your proposal for PyCon 2013!

Comments

pydanny said…
Unfortunately, you won't see Disney or Pixar developers speaking at conferences. Because of creative controls Disney puts on it's staff so they don't blow open the plots of movies that pay for a thousand people at a time, they heavily restrict their speaking engagements.

This also might be the case for Dreamworks and various American effect companies, but I'm not certain. From my experiences at PyCon New Zealand, I do believe WETA digital gives it's developers a lot of freedom.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...