<https://pantsbuild.slack.com/archives/CASMF8SJ1/p...
# general
m
Foursquare definitely has not completed a migration to Python 3.
h
Indeed, perhaps I should change that Foursquare link. That’s actually the blog written from me about Pants’s migration to Py3 when I was a Foursquare intern, which was to unblock Foursquare
m
I remember, friend.
❤️ 1
h
None of the functionality in this blog existed in Pants v1 btw. These features are all from things I would have died to have when working on Foursquare’s migration I’ve been talking to Mateo and Mathieu about possibly upgrading to Pants v2 for the Python portion of the codebase
m
I actually logged in to this Slack channel because I started half-heartedly looking into upgrading our pants instance from 1.7.0.
h
Woah, I had thought y’all were on something more recent. Let us know how we can help y’all upgrade. Things are much nicer and also faster now
Probably the biggest feature Foursquare engineers would like is dependency inference. Removes about 90% of BUILD files and about 30% finger grained cache keys. https://blog.pantsbuild.org/dependency-inference/ I remember thinking Pants was stupid when at 4S because of BUILD files 🙈
https://www.pantsbuild.org/docs/how-to-upgrade-pants-2-0#step-2-setup-jvm-node-and-go-support-if-relevant describes how you can have JVM still use an old version of Pants and have Python use something modern like 2.0 I remember Mateo and Mathieu had some trouble with JVM concurrency issues when upgrading; it may be much more tractable to only upgrade Python for now
m
I saw the post about BUILD inference. It seems like a great feature. I felt the same way about BUILD files when we first started using pants, but now I kind of like them. All our build files are auto-generated by a tool, and I think it is helpful to have a way of inspecting which packages have which dependencies. And it’s really nice to be able to see how dependencies change when reviewing a PR.