Hi @clever-pizza-88607 @stocky-fall-72490 @numerous-apple-46718 @enough-advantage-61561 @nice-tiger-10140 @loud-shoe-52387 @rapid-magician-69541 @red-lizard-87881 @green-match-60388 @acoustic-potato-34766 @clever-exabyte-16485 Welcome to the Pantsbuild community. We're eager to get to know you better. Can you share a brief introduction about yourself, your organization, what led you to Pantsbuild, and which specific features caught your attention? Don't hesitate to reach out if you need any assistance or have any exciting ideas to share!

Hi all. Background is in IOT with rust/scala/python/c++(bleh). currently at Dave(neobank) that is all cloud, which is a fun change. we are heavily utilizing airflow and apache beam with python and java(some day move to scala). we are also pushing forward with protobuf(usin buf). most of the company is in javascript/typescript/node land and the data side is all in python. have been irritated with tools like bazel and stuff in the past. too complex. interested in pants(v2) because it's python support is great(pex and pyoxidizer) and should be able to do buf, js/ts/node, and java/scala in the same repo. we have many individual repos but there is some desire to move to a more monorepo solution. i've been using poetry for most of my stuff and others here use pipenv. seems like pants can help us bridge that without disrupting too much. oh, and pex/pyoxidizer + containers(docker) is super exciting. i see some support for cloud functions, would be interested in cloud run support really the features from pants are: • easy binary(pex/pyoxidizer) that is as small as possible. this should allow us to deploy to serverless solutions and stream processing solutions much faster and with less ceremony. • cross-language support • lockfiles • easy extensibility(macros, adhoc, plugins(in repo or 'remote')) started on an issue in pyoxidizer support in pants to get support for custom index-urls. see this. i'm also

ryaminal

on github. apologies for this wall of text... oh, and huge shoutout to backend.ai. relied heavily on their utilization of pants for my own exploration at dave.

Hi all, I'm working at Equilibrium Energy with @modern-london-16641 & @curved-manchester-66006. I have a background in node, python, clojure, nix, a bit of c++ & rust, and now golang. I've worn both Software Eng, DevEx, and DevOps hats in the past and am now back on the SWE side of the fence but still dabble in build & deployment infrastructure and tooling. We're evaluating Pants v2 against other build tools (primarily Bazel) for our polyglot stack and hoping they help ease the process of migrating to a monorepo. Our stack is currently TS/Golang & Python, so Pants seems quite ergonomic; however, we are also hoping to start building or rewriting some components of our stack in Rust in the near future, so we're definitely interested in the progress of those features as well.

hello, i am also currently looking into pants v2 in comparison to bazel

Hi, Im working on a Data platform team of a fintech startup and planning to use Pants as our main Build system. Our plan is to use a monorepo and: • CI testing • Docker builds • Publishing Python packages Currently im in the phase of implementation and struggling a bit with caching. Seems like testing takes a lot of time in CI (using GH actions) Would love some help with realizing what im doing wrong and how I can run tests in CI which will be blazing fast 🙂

Feel free to post questions in #general!