<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: walnutgeek</title><link>https://news.ycombinator.com/user?id=walnutgeek</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 16 Apr 2026 15:40:37 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=walnutgeek" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Show HN: Lythonic – Compose Python functions into data-flow pipelines]]></title><description><![CDATA[
<p>I was thinking about something like this for years, few trys before this. Started this 
repo last year and I think I got something that usable now.<p>Async framework, mix sync/async python functions, compose them into DAGs, run them, schedule them, persist data between steps or let it flow just in memory.<p>GitHub: <a href="https://github.com/walnutgeek/lythonic" rel="nofollow">https://github.com/walnutgeek/lythonic</a><p>Docs: <a href="https://walnutgeek.github.io/lythonic/" rel="nofollow">https://walnutgeek.github.io/lythonic/</a><p>PyPI: pip install lythonic<p>It is dataflow. So theoretically you can compose it with pure functions only. Lythonic requires annotations for params and returns to wire up outputs with inputs. All data saved in sqlite as json for now, and it would work for some amount of data ok.<p>You may use it as task flow keeping params and returns empty and maintaining all data outside of the flow.<p>But practically you may do well with some middle ground, just flow metadata thru, enough to make your function calls reproducible and keep some system of records that you can query reliably.<p>Anyway I will stop rambling ... soon.<p>Python 3.11+
MIT License. 
Minimal dependencies: Pydantic, Pyyaml, Croniter<p>Prepping for v0.1. Looking of feedback. v0.0.14 is out. Claude generated reasonable docs. Sorry, I would not be able to do it better. I am working on Web UI and practical E2E example app as well.<p>Thank you.
-Sergey</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47757289">https://news.ycombinator.com/item?id=47757289</a></p>
<p>Points: 5</p>
<p># Comments: 0</p>
]]></description><pubDate>Mon, 13 Apr 2026 20:18:59 +0000</pubDate><link>https://github.com/walnutgeek/lythonic</link><dc:creator>walnutgeek</dc:creator><comments>https://news.ycombinator.com/item?id=47757289</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47757289</guid></item><item><title><![CDATA[New comment by walnutgeek in "Ask HN: Best API Documentation Tools?"]]></title><description><![CDATA[
<p>I know it is lame answer but I am very happy with Claude. I think it decide on mkdocs but it probably does not matter much.<p>My setup: There is bit of instruction in CLAUDE.md, with reference to full documenting.md startegy. If you are in python, consider doctest - documentation that doubles as unittest.<p><a href="https://walnutgeek.github.io/lythonic/" rel="nofollow">https://walnutgeek.github.io/lythonic/</a>
<a href="https://github.com/walnutgeek/lythonic/" rel="nofollow">https://github.com/walnutgeek/lythonic/</a></p>
]]></description><pubDate>Fri, 10 Apr 2026 06:49:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=47714446</link><dc:creator>walnutgeek</dc:creator><comments>https://news.ycombinator.com/item?id=47714446</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47714446</guid></item></channel></rss>