Pants is helping many software teams. Here's what some of them have to say.

Gordon Cassie

Head of Engineering, Legal Transaction Management


Over the last year at iManage Closing Folders, we transitioned a mature Django monolith with three accompanying microservices to Pants. Right off the bat, this transition forced us to untangle a convoluted web of dependencies that had emerged in our codebase over the six years it had been actively developed on. Soon after the migration we were able to get significant wins through codesharing between our monolith and microservices.

Additionally, the safety and speed of our deployment process was drastically augmented by Pants ability to build fully self-contained .pex files.

For day-to-day work, Pants has empowered developers to create clear separation of concerns between disparate parts of the application, eliminating unnecessary dependencies and improving stability and maintainability. It has also brought sanity to keeping linting, formatting, third party dependency versioning and python versions consistent across the codebase.

Compared to other build tools, Pants is drastically more approachable for a small team of python developers, making it possible for an early-stage company to lay the groundwork for a maintainable codebase at an early stage. Perhaps most importantly, it is backed by a passionate team who are an absolute joy to work with. I would recommend Pants highly to any team!

See also Gordon's case study writeup, "Putting Pants On: One Thing We Did Right After 5 Years with Django"

Alexey Tereshenkov

Software Engineer

We have rolled out Pants across the organization now replacing Conda based workflows. About 75 engineers will be using Pants almost daily via the CI and sometimes locally for REPL and run goal. Pants does magic and the feedback has been hugely positive. I am extending the internal docs as the feedback comes, but nothing major. It's running in CI producing Debian packages and friends, it's pure gold!

Raúl Cuza

Software Engineer


Pants makes our monorepo keep its promises. In theory, monorepos let any developer make improvements that impact multiple products. Big impact means big responsibility. Pants standardizes the steps, eases discovery, and highlights dependencies, tests, and other projects that are in the improvement impact area. Pants is how we keep do more good than harm with each PR. Pants is also being developed by one of the most helpful open source communities I participate in. They teach and unblock. There can be no higher praise.

Cristian Matache

Software Engineer

Python is the go-to language for most quants, but its flexibility is a double-edged sword. While seeing immediate results is great, it is quasi-impossible to tame the code as it grows large without several external tools: type checkers, linters, formatters, hermetic packers etc. I love Pants not only because it unifies all these in a few simple and swift commands but also because it adds hassle-free long-term value. Remember that "time is money", so save some for your future self and add Pants to your repos!

Lukas Haberzettl

Senior Software Developer

I must say, it’s a life saver. I was impressed with how easy it was to migrate our current projects to Pants. Documentation is well written and the example repos (example-python and example-plugin) are good starting points. Right now we use Pants to manage 5 of our projects and our development process has improved a lot, especially the CI pipeline.

Josh Reed

Senior Site Reliability Engineer

Seriously, the level of transparency and communication by Pants team members gives me immense confidence in Pants as a tool, because I have confidence in the team behind it.

JP Erkelens

Software Engineer

Pants has been instrumental in democratizing our organization's data platform. It's allowed us to define modern, reliable build processes that can be easily declared from a wide range of personas: from data analysts to software engineers to product managers.

Did this page help you?