问HN：数据工程师的单一代码库（Monorepos）？
大家好，我正在与一个数据工程团队合作，试图将他们所有的杂项项目整合到一个单一的单体仓库（monorepo）中。我习惯于在常规软件工程的背景下使用单体仓库（例如，在我的公司，我们的单体仓库使用的是Golang、Rust和Next.js，并且我们使用moonrepo来管理一切）；然而，在数据工程的背景下，我的经验就不那么丰富了。再加上我在Python方面的能力也没有达到应有的水平 : )。我想知道在数据工程的背景下，管理Python单体仓库时是否有一些已知的最佳实践我应该了解的？
查看原文
Hey folks, I'm working with a data engineering team trying to consolidate all their misc projects into a single monorepo. I'm used to working on monorepos in the context of regular software engineering (e.g. at my company, our monorepo is Golang, Rust, and Next.js and we use moonrepo to manage everything); however, not so much in the context of data engineering. It doesn't help that I'm not as Pythonic as I should be :). Wondering if there are known best practices I should be aware of for managing Python monorepos in the context of data engineering?