I'm interested, right now, in 1. Incrementally converting our existing setup to pants to fix our dependency woes and 2. Authoring a plugin for the Serverless framework to make it easy to deploy Python lambda functions in a monorepo setup

Hi @happy-kitchen-89482 Unfortunately it seems that I've missed your message. Sorry. I'm not familiar with Moshe, we are near 1000 people here in Tel Aviv, but I will try to find him and talk to him. Thanks!

Welcome to @elegant-salesclerk-19767 @nice-park-16693 @lively-garden-66504 @cold-art-1116 @rhythmic-lunch-93199 @green-tiger-17672 @fresh-garden-39510 👋. We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

Welcome to @ripe-gigabyte-88964 @kind-eve-37117 @square-laptop-33187 @silly-waitress-33423 👋. We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

Hi, started looking into Pants for Docker build. It has a few time consuming layers (e.g. library installs or loading data), a few stages to save, and Docker’s remote cache is not solving the issue. Hopefully I can figure out how to efficiently and smoothly build these images with Pants.

Welcome @worried-addition-27578 @numerous-xylophone-26710 @adorable-secretary-13727 @stocky-exabyte-85041 @average-father-89924 @best-judge-92368 @calm-answer-22209 👋. We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

Hi, I'm the lead engineer at a startup called Medasync. We're migrating over to a mono repo solution for our python backends and decided on pants to manage the builds. I recently started on a new project to kick off the mono repo. I'm still getting used to the workflow and its quirks, but I'm mostly liking it so far.

Welcome to @damp-needle-81549 @busy-energy-26374 @glamorous-analyst-68555 @most-advantage-18294 @important-tiger-35583 👋. We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

👋 Ahoy! I'm the web developer at a lumber and land company HQed in Alabama, The Westervelt Company. I'm mostly a team of one, though I do have a backup in our DBA and we do outsource a lot of the frontend work through an external consulting company. I've spent the past couple of years migrating a bunch of our ColdFusion legacy applications to Python, Django, and React. However I'm starting to feel the operational complexity of Django+React is not worth it for the types of websites and applications I build and am exploring using Django beyond just an API server, e.g. using the builtin templating system and a light JS framework for sprinkles of interactivity plus HTMX for an SPA feel where applicable. I'm giving Pants a try as I've really enjoyed the monorepo approach for all of our frontend code using Turborepo. I'd much rather deal with a monorepo then the multirepo approach with the different Django projects and the maintenance overhead of either copy-and-pasting shared code between the projects or splitting out the shared code into dedicated modules that are published to an internal PyPI.

Hi there, I'm a Data Infrastructure Engineer at a startup pharma company called Empirico! My team helps try to improve development workflows and tooling for data scientists / engineers and bioinformaticians. Our scientists often have use cases for creating python analyses with different environment requirements, and we've been struggling to figure out how to manage these in an efficient manner. We really like the monorepo approach, but it's obvious that this could get really hairy really fast without some advanced tooling, so I'm looking to Pants to help manage some of that complexity. I've never really used a build tool extensively though, so I expect to be asking a lot of beginner questions. Pants seems very powerful

Hello, I'm an ASIC/FPGA engineer currently working at IBM but I like to work with hardware in my hobbies too. I'm hoping to use pants as a solution to really challenging hardware based problems for build flows.

Hello, I'm an engineer at BNP Paribas, a French bank. I lead a team of data scientists and engineers using new types of data for risk modelling and portfolio monitoring. We've been migrating to a monorepo, and starting to use pants to manage our various build tasks.

Well, hello @fast-belgium-77939.

Welcome to @loud-spring-35539 @quaint-oyster-63068 @billions-toddler-84781 @adamant-umbrella-55437 @hallowed-hairdresser-79957 @freezing-flag-32480 @careful-postman-22473 @fast-belgium-77939 @loud-chef-48543 @wide-egg-20352 @broad-dentist-80514 👋. We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

Welcome to @famous-horse-60120 @quiet-evening-74533 @bumpy-arm-17246 @limited-advantage-17894 @high-umbrella-90955 @blue-city-46130 @dazzling-dress-95246 👋. We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

Welcome @enough-insurance-9138 @mammoth-area-83300 @dry-daybreak-49731 @microscopic-lamp-95570 @breezy-mouse-20493 @bored-orange-30421 👋. We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

Hello! I’m a lead engineer at Fathom - most of my work centers around data engineering, MLOps, and developing deep learning models. We have a few Python repos which grew organically (i.e. not much structure with regards to packaging best practices) to be large and slow, and I started looking into Pants as a way to bring some structure and speed to our CI

Hi all, I'm a Machine Learning Engineer at Vivun and am mainly working on the mlops side of things for our data science team. We have a good amount of repo sprawl with poorly managed python packages and dependencies, so currently I'm working on a POC for a data science oriented monorepo that will hopefully get us out of dependency hell and to a place where we will be able to release incremental changes with confidence and speed. And of course I'm thinking that Pants will be a major tool in our toolbox to achieve these goals

Hi folks. I'm a Software Engineer at Viva Republica, developing the backend and infrastructure for the Toss service. Our team mainly uses Python and Go, and we are testing Pantsbuild to integrate and manage dozens of server repositories, fragmented CI/CD pipelines, package management, and code in one repository. Thanks :)

Hey! I’m a Principal Cloud Engineer at Medtronic, and the tech lead for the Developer Experience team within the Cardia Rhythm Management (CRM) org. I started using pants when I looked for an integrated build system after I left my position at AWS (they use an internal system called Brazil). I really loved that system, as the amount of boilerplate code was SO small; a single BUILD file was enough. While I know many use multiple BUILD files with pants, all of my current repositories only have a single BUILD file, and I get along great! I’ve spoken to a few other teams here in CRM and they have expressed interest in utilizing a built system, mainly for remote caching and execution. I’ve not set that up yet for us, but that is because teams need JavaScript/TypeScript support and .NET support. I plan on providing a few cycles this summer to tackling a .NET backend with another Principal engineer colleague who has years of .NET experience (I’m bringing the years of Python experience).

Welcome to @ripe-dress-3165 @ancient-lawyer-12557 @narrow-furniture-61039 @boundless-ambulance-11161 @clever-battery-17783 @polite-art-32636 👋. We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

Hi, I'm the leader of the machine learning team in an early stage startup (Aviva credito, offering loans in underserved areas of Mexico). I knew I wanted a monorepo (to avoid the pain of having to do coordinated PRs, with coordinated tests when making breaking changes), and we will only use python for the foreseeable future. The choice of Pants comes from 3 constraints: • Build time (especially in CI). I've worked in start-ups where any commit added to a PR would trigger a 40 min build in CI, that made the PR review process extremely tedious. I knew I wanted a build system with a fine-grained cache invalidation. (the tools I had heard of for this were Pants and Bazel) • I have utilities packages (which are general, will probably be used in several projects), and projects packages. I wanted a single lock for the 3rd party dependencies, to ensure all packages can work together. But I also want them to be separate packages, to avoid having to install the huge deep learning libraries when working on a project which does not require our deep learning-related utilities. I first looked into handling this central lockfile with poetry but it seemed surprisingly hard. So I was happy to see it was easy in Pants. • Nobody in our team has experience with build systems and CI pipeline. So we wanted something simple to put in place and maintain. That was another advantage for Pants over Bazel (which seems more complex). We switched to Pants this week. But we still have some pain points: • Because I generated the lockfile on my laptop, the torch version is "torch-1.13.1%2Bcu116-cp310-cp310-linux_x86_64.whl". Which works fine in production (also on Ubuntu with same CUDA version). But we discovered that the build fails on my coworker laptop (Mac OS without GPU). I think it's related to this issue. I'm looking into solutions, probably multiple resolves corresponding to the different environments. It might lead to different versions of the other packages, so it wouldn't be a perfect fix, but better than some team members not being able to reuse the lockfile. • I'm struggling with the installation of a Build-Farm build agent (problems unrelated to Pants). I'm considering Toolchain, but the price looks a bit steep coming from Mexico (salaries are lower than in the US/EU, so it makes more sense to use a cheaper solution, even if it requires more work to get it to function). It's not clear to me, what advantages does Toolchain bring, compared to self-hosting Build-Farm (outside of the ease of setting it up). • [Edit: now solved, thanks to @enough-analyst-54434] Waiting for the Build-Farm build agent, we use the default build agent from Azure. But caching of "named_cache" only works sometimes. It seems due to the size of the cache (21G because it seems to duplicate the libraries, the virtualenvironment is only 7G). I did not get an answer to my question (https://pantsbuild.slack.com/archives/C046T6T9U/p1681276057778189) so I'll continue investigating.

Thank you @busy-vase-39202. Hello all, I'm Raph, and I lead the engineering team at Nory - we make software for restaurants. I'm experimenting with Pants and a monorepo for our various (mostly) Python services. I've found Pants' native support for python and the ability to decouple, selectively build and package parts of the codebase to be very powerful. The main challenge I've hit with Pants so far is related to cross-building: • our dev machines are macOS ARM • our CI (GH Actions) is linux x86_64 • our production environment is linux ARM (AWS Graviton) Normally I'd build the projects directly into their docker image, which then works well in CI and production thanks to buildx. But since with Pants, PEX files get built before the docker images, and Pants does not seem to support docker buildx, I haven't found a good solution for my team yet. Would love to speak to anyone who has a similar setup and has found a good recipe - I'd really like pants to work out for us.

Welcome @great-parrot-43150 @acoustic-agent-66612 @gifted-autumn-61196 👋. We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

Hi all, I’m Moritz and I am heading ML and engineering at beyondwords.io. We offer text-to-speech (TTS) services and are aiming to consolidate our TTS stack into a mono-repo for various reasons: • better manage cross-service dependencies and contract testing • streamline development and delivery workflows • Improve code visibility and collaboration We are looking into Pants to support this effort, specifically to: • shorten local commit cycles • shorten CI build times • improve developer UX (currently using Make) There is a vision piece, where we want to treat ML model training as build steps and manage ML workflows with the build system rather than relying on orchestration tools such as airflow. I am currently investigating how execution and caching of remote tasks and artefacts would work. I would be interested to know if anyone has or is planning to use Pants in a similar way 👋

Hello, I'm Ryan Draves, a software engineer at Astranis. I like to mess with our tooling for fun. @high-yak-85899 is our Pants guru that found and setup the tool for us, but I thought I'd join here as well for a quicker relay on some questions I had.

Welcome @rough-car-32571 @bright-dress-58216 @great-waiter-81135 @narrow-salesmen-47225 @helpful-father-21431 @brash-area-42337 @blue-fish-75687 @enough-stone-26192 @mysterious-journalist-32264 👋. We invite you to say a little something about yourself and your organization, and what motivated you to take a closer look at Pants. You’ll be helping us improve future open source outreach, so thanks very much!

Wow, how neat! I don't think we've had such use case come up before. It would make a fascinating case study, once you've got it all setup. Meantime, of course feel free to ask as many questions as you need to. We appreciate learning from users's questions and feedback!

I hope to learn a lot from everyone here and to have a smooth understanding of pants and a smooth trouble shooting of pants issues

Hi everyone 👋 At Forter we’re working on revamping our mono-repo infra using Pants, an effort led by @high-magician-46188. I’m looking into the Docker and Helm integrations as we have a concurrent effort of moving services to K8s. It raised a few interesting issues around how we can do CD with a PR-heavy mono-repo, so I’m here to keep tabs on that effort and progress of relevant features 🤞