https://pantsbuild.org/ logo
Join Slack
Powered by
t
message has been deleted
h
Just landed, will lurk as long as I can, but can't participate actively
Welcome Australian friends!
c
h
Notes doc is linked from the calendar event btw
w
c
No one screamed, so I hope this mic setup is working!
👍 2
g
I just moved most of our monorepo over to pants (3 weeks-ish) and I'm running dev. My plan in the future is to use pants stable on main and when prepping to upgrade have a parallel version running in pipelines for a week or so to ensure results are the same.
h
Checking that someone is updating the notes?
👍 1
b
c
Could also add it in the doc on contributing
👍 2
c
(phone too hot! brb)
🔥 1
c
Speaking of stabilisation: The lockfile and export goals are being/need to be renovated
👍 1
So idk how much of that end we can stabilise
Adding to the challenge of stabilising is that most of Pants leverages parts of the Pants python backend to run (eg the rules for running a PEX are needed for most backends to run tools, which ends up pulling in all of lockfiles)
Does anyone have thoughts about the way JVM tools do lockfiles vs python? JVM still uses the old style (can change things in pants.toml) but python uses user resolves
Take care everyone!
w
@careful-address-89803: afaik, JVM uses user resolves too: it actually did first I think
w
Adding to the challenge of stabilising is that most of Pants leverages parts of the Pants python backend to run (eg the rules for running a PEX are needed for most backends to run tools, which ends up pulling in all of lockfiles)
Semi related, I think we talked about it being cool if there was some way of doing lazy loading of backends, so if you didn't explicitly need one, there was no slow down due to backend loading
c
I think tools use a separate path, you can still specify the version and the lockfile path in pants.toml and generate lockfiles without needing to declare anything in a build file
w
the one bit of prior art from 1.0 that might be interesting was that we did a survey of types used in people's repos and in thirdparty plugins (iirc it was roughly: "run this command to collect import statements, then sanitize it and put it here"), and then we stabilized most-but-not-all of them
I think tools use a separate path, you can still specify the version and the lockfile path in pants.toml and generate lockfiles without needing to declare anything in a build file
oh, tools. sorry, don't know
3 Views
Open in Slack
PreviousNext
Powered by