https://pantsbuild.org/ logo
Join Slack
Powered by
Hi Pantsians, my name is Jessica. I’m a sr. softwa...
# welcome
e
Hi Pantsians, my name is Jessica. I’m a sr. software engineer at Delta Air Lines and brand new to pants. Our team is converting one of our internal app repos into a monorepo in preparation for several new sub-apps (each with its own aws cdk app) to be imported / developed in parallel by other teams… I’m liking pants a lot so far for formatting and running tests… I’ve dabbled a tiny bit into writing plugins, but still have a lot to learn. I’m working on an example monorepo that uses pants, and one main priority is to have clear instructions for new devs that may only be concerned with adding code to one of the sub apps… trying to find the smoothest process possible so the teams are enabled to deploy and work within their namespace freely while our core team maintains visibility on the app as a whole. I just discovered I can export the resolves to venvs, which is neat. The reality is that the different sub-apps don’t have a need to share dependencies… but I am starting to see how it will make things easier to resolve to the python-default lockfile unless there is a reason not to. Shared dependencies would be a slight paradigm shift for the project, where each package currently has its own requirements.in file that is compiled on changes. Anyway… just trying to wrap my head around all of it and strike the right balance between governance and autonomy for the teams. Thanks for hosting this channel, and I look forward to leaning more. 👖
👋 8
b
Feel free to ask away in #general we're a friendly bunch. Also happy to hear when things are working well... or not 🙂
❤️ 1
h
Welcome! I've not previously seen "pantsians" used but I like it.
👍 1
The paradigm shift you mention is encountered by so many Python devs when first switching to a monorepo model, so I definitely understand that this takes some getting used to. I firmly believe it is worth it to have one (or a small handful) of resolves for the entire repo, rather than one per project, though. Of course this requires a tool that knows how to take appropriate subsets of the requirement universe. Enter Pants...
We can provide good arguments, should you need to make them to your team :)
❤️ 1
e
Thanks, that’s very kind :) If you happen to have any articles handy, I’d definitely be interested in some perspectives around that.
h
I'll be speaking about (among other things) this very topic at PyBay on Oct 8, I hope they video it
e
Nice, I hadn’t heard of PyBay— sounds fun… maybe I’ll check it out.
c
h
Ah but this is as a collective noun!
😇 1
Open in Slack
PreviousNext
Powered by