GitHub user sshiv012 added a comment to the discussion: Two efforts to convert a Python program to a Texera workflow
Thanks for laying out the tradeoffs. Since the LLM-based notebook migration tool is already merged and relatively stable, could we first clarify the user need that requires a second Python-to-workflow path? The compiler’s equivalence guarantee could be valuable, but I’d like to understand which users or programs need that guarantee, and whether the current LLM approach falls short for them. Before we commit to maintaining both approaches, could we define a small set of representative use cases and compare the results, including correctness, usability, and maintenance cost? If the compiler addresses a clear gap, that would make the case for supporting both much stronger. GitHub link: https://github.com/apache/texera/discussions/8521#discussioncomment-18575029 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
