yeah

if that's not best practice I can change

no, definitely should!

Hi all: What happens to the dependencies section in pants v2?

I've been tinkering with the "fmt" goal. I have configured black and isort as per the documentation. When I run:

./pants fmt ::

isort alters "subfolder/app.py" and properly separates my third party imports. If I run:

./pants fmt subfolder::

or

./pants fmt subfolder:lib

isort alters "subfolder/app.py" and puts all my imports back together. Guessing I should see the same behaviour in both cases? Running pants==2.2.0 and isort==5.7.0

hi all, i was thinking about adding a new autoformatter: autoflake, would you recommend adding it on the main pants repo or creating a separate repo?

hello! this is probably a dumb question but is there a way to figure out why some files are not being included as dependencies if I am relying on dependency inference? for example if I have

src/BUILD

python_library(
    name='server'
)

src/app.py

which imports

fraud.api

I would assume that fraud/api.py would be included in the

./pants dependencies --transitive src:server

output? However it is not present - (it is very possible that I am misunderstanding the dependency inference capabilities)

Issues building pants (NOTE for everyone): I've been using Pants for 3 years now. In the past year, I've tried updating Pants a few times and always got an error (but the reason WAS NOT Pants). Fast forward one year later, I got a new computer and installed Arch Linux on it (my previous system). With a fresh install of Arch Linux, I still couldn't get Pants to install. It would hang on Collecting psutil==5.7.0 Using cached psutil-5.7.0-cp38-cp38-linux_x86_64.whl Realizing Arch Linux had issues with just building a make package, I tried to boot Arch Linux from a USB drive, log in to my account (aka chroot), and then build Pants. And it worked flawlessly. The point is that several things can be broken in your system, preventing Pants from updating or being installed. In that case, try booting from a fresh USB drive and then do your updates.

Glad to hear it's working now! Let us know if you have any questions or suggestions with Pants 🙂 With the issue building downstream deps like psutil, you could also try consuming Pants as a Pex: https://www.pantsbuild.org/docs/proxies#installing-pants

Proxies looks like a good method. I will definitely try this in the future, but I'm kind of worried it will install extra dependencies on my system. Will it?

The proxy isn't the relevant part here, the docs only happen to be on that page I mean the section about installing from a Pex - that means that all the dependencies are already bundled into a single binary file. You don't need to install things like

psutil

because it's prebuilt for you

Oh, ya that's what I understood, a pre-build bin. But wouldn't that mean you have to download a larger file, with all the dependecies? (I'm not entirely sure how Python would do it.)

I'm kind of worried it will install extra dependencies on my system. Will it?

Depends what you mean - Pants will download things like Pytest and your 3rd party dependencies so that it can run these tools, but that happens in

~/.cache/pants

and won't leak into your system If you install Pants via the

./pants

script, pip will also install Pants dependencies into

~/.cache/pants/setup

. If you use the Pex approach, that part is skipped

But wouldn't that mean you have to download a larger file, with all the dependecies?

Indeed. Although, with the normal

./pants

script, pip will still have to download those deps either way (unless already cached)

Ahh, good point. I will have to try that in the future. Thanks for letting me know this!

Has pants2 have jvm support yet?

I just recently came across the Please build system and was curious if any of the folks here had thoughts on it. https://please.build/

qq, we’re trying to run django with its autoreload functionality in pants v2.2 but the way that django performs the autoreload looks like it’s spawning a subprocess and copying the environment. https://github.com/django/django/blob/master/django/utils/autoreload.py#L250-L256 In doing so it is failing saying it can’t load the

django

module. Seems like it’s losing sys.path information. I tried using

--loop

and disabling the django autoreload functionality hoping pants could do that for me but when testing a file change pants wasn’t restarting the run goal. Any ideas?

hey Nate: this is related to https://github.com/pantsbuild/pants/issues/9462#issuecomment-716821870

as it mentions, goals are not interruptible in general… but we’re hoping to allow that to be configurable soon

@helpful-lunch-92084: would you mind describing the whole usecase on the ticket? it will help a lot with implementing it in a useful fashion

we’re hoping to tackle it before this summer, but we might be able to bump it up a bit, because it’s not a ton of work

sure

so just to be clear, just add a +1 and our use case in the 9462 tkt?

that’s right

q, if this functionality were added, would it be possible to backport it to pants 2.2? I ask because right now we’re in a tough spot where we still have a bunch of py2 code and we can’t enable the 2020-resolver due to it being horribly slow on py2 and we can’t upgrade to pants 2.4 since i’ve heard it drops support for the pip legacy-resolver.

2.2 would be a bit of a stretch, but… maybe 2.3 though?

ok

i expect that if we were going to extend support for a “pre-resolver removal” version, it would likely be

2.3.x