if someone with admin privs can review, merge & sync https://github.com/pantsbuild/binaries/pull/32 it’d be much appreciated 2 replies Ah, sorry - got confused. You did commit new 4.9.0 binaries ... now synced.

thx!

I see in my 3rdparty/jvm dependencies a reference to

scala_jar('org.scalatest', 'scalatest', '3.0.3', 'test')

, and I think it might be an instance of python truthiness hurting me

because I think that last parameter 'test' is nonsense judging by the JarDependency documentation (it seems like it would match the

force

boolean parameter

and a string might be interpreted as

True

and thus I'd never notice

I think someone assumed that it was a scope parameter, which instead lives on the jar_library

Your diagnosis is correct.

cool, I'll move the scope up to the parent

jar_library

, thanks

hi, does pants bootstrap its own pip? or just its virtualenv?

virtulenv’s

hi, anyone around that is familiar with using pants with the node contrib plugin that could help me? I'm trying to convert a co-workers node project to using pants and I was wondering what the best practices/way to depend on other projects within a monorepo. I was trying to use pants BUILD file dependencies but this comes up with a warning saying that its not fully supported. Also I'm getting an exception saying:

'Target' object has no attribute 'version'.

I have checked all my thirdparty BUILD files have version specified. But if I use their

package.json

with

npm-shrinkwrap.json

or

yarn.lock

I have a hard time getting the relative pathing to work like file:../../etc Any advice, guidance, pointing in the direction is greatly appreciated!

cc @brash-cricket-7489 ^

@stocky-portugal-83098 I might be able to help you if I have a little bit more information, you can direct message me

thank you for the answer. so to set the pip version i would do it in python's 3rdparty requirements?

because I see

Step 6/15 : RUN /opt/app-root/src/pants -V
 ---> Running in c95ba13e30b2
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0   122    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   281  100   281    0     0    330      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 1802k  100 1802k    0     0  1750k      0  0:00:01  0:00:01 --:--:-- 1750k
New python executable in /opt/app-root/src/.cache/pants/setup/bootstrap-Linux-x86_64/pants.CMlwzD/install/bin/python2.7
Also creating executable in /opt/app-root/src/.cache/pants/setup/bootstrap-Linux-x86_64/pants.CMlwzD/install/bin/python
Installing pip, wheel...done.
Collecting setuptools==5.4.1
  Downloading setuptools-5.4.1-py2.py3-none-any.whl (528kB)
Installing collected packages: setuptools
Successfully installed setuptools-5.4.1
You are using pip version 8.1.2, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Collecting pantsbuild.pants==1.3.0

it's installing pip

I found that the pip version is dependent on virtualenv version.

what are you trying to do, exactly?

afaik, you can

pip install --upgrade pip

in a venv and it’ll bump the inner pip version

but maybe bumping the venv version is more appropriate - I have no idea what your goal is tho

what’s the equivalent of sbt ~ compile for pants

and ~ test

how do I generate ensime config into .ensime folder, the standard location?

visual studio code ensime server isn’t picking up on

./pants ensime ::

are you trying to squash this error message?

You are using pip version 8.1.2, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

I would not sweat that, imho

yeah, i'm not trying to do anything- one of our se's was curious why the version was low, i didn't hvae an answer for him 🙂

Here’s a funny idea for lint / fmt. Could fmt use lint’s invalidation status?

lint may accept things that fmt would change even given the same configuration. Also, that way if a CI were to run lint but not fmt, then fmt would only run on targets that had invalidated lint calls.