<story><title>Go Python, Go: Stream Processing for Python</title><url>https://blog.wallaroolabs.com/2017/10/go-python-go-stream-processing-for-python/</url></story><parent_chain></parent_chain><comment><author>dajonker</author><text>What about the use of Pony? I did not hear about it before but I do like some of the ideas of the language I read on their website. However, they also state &amp;quot;Pony is pre-1.0. We regularly have releases that involve breaking changes. This lack of stability is plenty of reason for many projects to avoid using Pony.&amp;quot;
How are you going to deal with that?</text></comment>
<story><title>Go Python, Go: Stream Processing for Python</title><url>https://blog.wallaroolabs.com/2017/10/go-python-go-stream-processing-for-python/</url></story><parent_chain></parent_chain><comment><author>harel</author><text>While the comments about being pythonic are valid, I think this looks fantastic and I&amp;#x27;ll take it for a spin around the block. Are you using this in your production environment already?&lt;p&gt;In regards to the &amp;#x27;name&amp;#x27; being a function - a class attribute might indeed be more correct but a function allows for dynamic computation names where its applicable.</text></comment>