<@U02KAN6061E> Here Nadir, Principal Engineer at <...
# welcome
a
@bitter-ability-32190 Here Nadir, Principal Engineer at trustmi.ai, working on python since 2014, happy to join Well I was planning to have a python monorepo for the organization and I wanted to keep it simple in the beginning multiple poetry projects but... as I started to work on it felt wrong to write all that scriptology myself and started a research on tools and how to achieve it (having in mind conventional commits which is the plugin I'm developing and the reason I joined) started my POC on google's Bazel but even selecting specific files was hard (for some reason it didn't worked), also it felt not so python oriented and then discovered
pants
made the comparison, started the POC and voila everything work as expected all the dependencies were in the right place, even cross project and transitive dependencies, the learning curve for a basic working project was easy the built in python backends were the deal maker.
b
๐Ÿ‘‹
the built in python backends were the deal breaker.
Mind elaborating?
a
Copy code
backend_packages = [
    "pants.backend.plugin_development",
    "pants.backend.python",
    "pants.backend.experimental.python",
    "pants.backend.experimental.python.lint.ruff",
    "pants.backend.python.lint.docformatter",
    "pants.backend.python.lint.pyupgrade",
    "pants.backend.python.lint.isort",
    "pants.backend.python.lint.black",
    "pants.backend.python.typecheck.mypy",
]
b
Ah, maybe I misunderstood what you meant about "dealbreaker"
a
the deal breaker to choose pants I meant
b
So the good kind ๐Ÿ™‚ Well, happy to have you! ๐Ÿ™‚
๐Ÿ™ 1
w
โ€œDeal makerโ€
๐Ÿ™‚ 1
h
This is great to hear!