PyCon-2015-sprint-wiki: Difference between revisions
Content added Content deleted
(add streamparse project) |
|||
Line 153: | Line 153: | ||
List of useful skills: '''"Participating is only feasible for people that can already at least roughly read C-code. Experience in C programming is recommended, but there are also refactoring and code-arrangement and cleanup-tasks that can be done by moving existing code around; that's why reading C-code is already enough for some tasks. In addition to improving C-skills I provide guidance for and insight into Python's C-extension API and also into Jython, how to use it, how it works."''' |
List of useful skills: '''"Participating is only feasible for people that can already at least roughly read C-code. Experience in C programming is recommended, but there are also refactoring and code-arrangement and cleanup-tasks that can be done by moving existing code around; that's why reading C-code is already enough for some tasks. In addition to improving C-skills I provide guidance for and insight into Python's C-extension API and also into Jython, how to use it, how it works."''' |
||
=== streamparse === |
|||
At this workshop '''Andrew Montalenti''' |
|||
List of useful skills: '''Python; interest in Apache Storm / Apache Kafka; stream processing, data analytics.''' |
|||
People of all experience levels welcome: '''Yes''' |
|||
Details about sprint tasks (if supplied): '''We'll be writing a Python Topology DSL for Apache Storm. This is a generic way to specify a direct acyclic graph of computation for data pipelines, which can then run Python code remotely on a cluster of machines -- thus defeating the GIL and allowing true concurrency. The plan is to use some fun Python features in order to write a good-looking DSL, e.g. I suspect metaclasses and descriptors will be involved.''' |
|||
== Info about the intro event == |
== Info about the intro event == |