Ah, so Pants 2.11.x introduces a new kind of lockfile: a PEX (JSON) lockfile. When 2.11.x goes non-rc I recommend trying ti out 😃 In the meantime your options are

resolve_all_constraints

or not.

I am just wondering why it only happens for MyPy? I dont see the same for isort/black/etc.

Good question! Formatters like

isort

and

black

don't require any of your dependencies to run. linters/checkers like

pylint

or

mypy

do require dependencies, so you just happen to be executing your first command which requires deps.

Thanks. It is clear to me. Btw, is there any docs already available on the new PEX lockfile in 2.11?

Another question is about, when Pants will re-build the mypy.pex and install those dependencies? Does it only run once, or it will only run when pants detects some change in the dependencies? From my observation, it does not happen everytime when I run

pants check

.

(Don't forget the

mypy.pex

just contains mypy and friends (and not your deps)._

But for the

pex

containing all of your deps. Yes that'll only rebuild when your lockfile changes

I am updating our docs for pants 2.11 this week, so we will have docs soon about the new pex lock files

This is probably easy enough to test out, but maybe someone already has a quick answer. Let's say in one repo I want to make a distribution (D1) that includes modules A and B and another distribution (D2) that includes modules B and C. Now, in another repo, I want to depend on both D1 and D2. Does that cause problems given the mutual definition of B or are they isolated in some way?

Hey Team, I think may recall a past suggestion for a feature/plugin that would prevent unwanted dependencies between targets. For example, if we have two modules

a

and

b

and want to prevent

b

from ever depending on

a

we can use a feature/plugin to do this. Does something like this already exists?

Does pants provide anything out of the box for knowing if something like a version number for a python distribution, docker image, and other artifacts needs to be bumped? In our monorepo, someone might change something in a shared library and not realize that they should have bumped version numbers for the dependent packages.

I am looking to do some processing of pylint output, which would be much easier if it were written to a file. I can give pylint an --output or --output-format option, which will write to a file, but I suspect this will not work well with pants' concurrency. Ideally there would be some way I could insert the current execution slot into the file name, like with pytest. But that would require having support for that env variable in pylint and a way to use it.

This is related to https://github.com/pantsbuild/pants/issues/14983, but when a pex depends on a distribution, does that do something funny with the module used for

entry_point

? I'm seeing my module specified as

entry_point

somehow end up in a traceback like

/home/nathanael/.pex/installed_wheels/64f793b8414b45d023fab18cdb41b8298ed2f8d103ec032118f40b5ad1289e2f/my_distribution-0.0-py3-none-any.whl/path/to/my_module.py

since when could we use for loops and variables in BUILD files?

We are deploying containers to AWS Lambda. Currently it is done using bash scripts after creating a pyx archive (unarchiving and copying into the image). Is there a Pants target for this?

TIL that pex is mentioned in the Spark documentation as one way to deploy to a cluster: https://spark.apache.org/docs/latest/api/python/user_guide/python_packaging.html#using-pex

Hey Team First of all thanks for developing Pants 🙌! We are moving to a monorepo and think pants would solve quite a few of our issues But i'm having a bit of a hard time making it work for our structure. I have the below structure

-- pants.toml
-- helloworld1
  -- src
    -- functions
      -- BUILD
      -- plus.py
-- helloworld2
  -- src
    -- functions
      -- BUILD
      -- plus.py
-- helloworld3
  --src 
    -- functions
      -- BUILD
      -- plus.py
      -- multiply.py
    -- function_tests
      -- BUILD
      --test_plus.py

In

helloworld3/src/function_tests/test_plus.py

I have

from src.functions.plus import foo

I need this import to be from the

helloworld3/src

path. When i run the test file test_plus.py I get this error

ModuleNotFoundError: No module named 'src.functions'

I'm also getting warnings like `The target helloworld3/src/function_tests/test_plus:tests imports

helloworld3.src.functions.plus.foo

, but Pants cannot safely infer a dependency because more than one target owns this module, so it is ambiguous which to use:`

['helloworld3/src/functions/core/plus.py', 'helloworld2/src/functions/core/plus.py', 'helloworld1/src/functions/core/plus.py'].

I have a pants.toml in the root folder which has

[source]
root_patterns = [
  '/helloworld1/',
  '/helloworld2/',
  '/helloworld3/',
]

Is this the correct way of setting things up? What am I doing wrong? I think my understanding of pants targets and sources hasn't 'clicked' yet, hopefully you can also help to make that right 🙂 Thanks in advance! Obviously i've replaced the real filenames with fake names. If that is not enough then please do shout and I'll look into creating a stripped down example monorepo with this error on github.

Hello, i’m new here, looks like theres interest to have someone contribute to the JS integration. i’m keen to help out

Hi, is such INFO duplication expected from

./pants lint ::

? Please check 🧵 for the

pants.toml

./pants lint ::     
18:05:08.06 [INFO] Completed: Lint with Flake8 - flake8 succeeded.
18:05:08.06 [INFO] Completed: Lint with Flake8 - flake8 succeeded.
18:05:08.06 [INFO] Completed: Lint with Black - black succeeded.
All done! ✨ 🍰 ✨
8 files would be left unchanged.


18:05:08.06 [INFO] Completed: Lint with docformatter - docformatter succeeded.
18:05:08.06 [INFO] Completed: Lint with Black - black succeeded.
All done! ✨ 🍰 ✨
69 files would be left unchanged.


18:05:08.06 [INFO] Completed: Lint with autoflake - autoflake succeeded.
18:05:08.06 [INFO] Completed: Lint with docformatter - docformatter succeeded.
18:05:08.06 [INFO] Completed: Lint with autoflake - autoflake succeeded.
18:05:08.06 [INFO] Completed: Lint with isort - isort succeeded.
18:05:08.06 [INFO] Completed: Lint with isort - isort succeeded.

✓ autoflake succeeded.
✓ black succeeded.
✓ docformatter succeeded.
✓ flake8 succeeded.
✓ isort succeeded.

Has anyone here stored pex binaries in Artifactory? Looking to get some insights before we start doing that in the near future.

What's the origin of the name "pants"?

Has anyone used

pants publish

to deploy a cloudformation template? Is that possible? I'm looking into using

pants package

for bundling a lambda function.

Anyone running into issues stemming from the new git security patch?

Is there a way to set a default value for a target type in pants.toml? I am starting incremental adoption of mypy in our repo was hoping I could set

[mypy].skip=True

in pants.toml and then start setting

skip_mypy=False

on each target that is ready. When I do this it seems that the pants.toml config is a global setting and always wins, rather than the default value I was hoping for. The alternative is to use tags, which we did for tests and lint, but that requires more complex filtering logic on every run.

Hi, I am trying to upgrade to pants

2.11

from

1.30

. I got a lot of errors like this:

Name 'python_library' is not defined.

What should I change them to?

Hi team. We have a repo that is structured as below:

- src
    - dir1
      - subdir1
        - script1.py
      - subdir2
        - script2.py
      - BUILD
    - dir2
      - subdir3
        - script3.py
      - subdir4
        - script4.py
      - BUILD

Is it advisable to have a

BUILD

file for each subdir as well? Given that we never intend to package/test the different subdirs separately? I feel that having a

BUILD

file at each subdir is unnecessary given we are happy with the defaults, and can be added later if we ever do intend to package/test/etc. those subdirs separately.

Hello, Has anyone encountered discrepancy in output when running

flake8

on its own and comparing it with

./pants lint ::

? For example, when I run

flake8

, I get:

file1.py:17:21: ANN201 Missing return type annotation for public function
file2.py:10:32: ANN201 Missing return type annotation for public function

However, when I run

./pants lint ::

, I get:

11:38:23.22 [INFO] Completed: Lint with Flake8 - flake8 succeeded.
...
✓ flake8 succeeded.

Is there a way to get more verbose output of

./pants lint ::

? So as to see what files are linted, what flake8 config, etc.

Does

[flake8].extra_requirements

require Pants version 2.11? I am getting the following error:

151429.26 [ERROR] Invalid option ‘extra-requirements’ under [flake8] in /path/to/project/pants.toml

151429.26 [ERROR] Invalid config entries detected. See log for details on which entries to update or remove.

(Specify --no-verify-config to disable this check.)

And my

pants.toml

has the following flake8 config:

[flake8]
config = ".flake8"
extra-requirements.add = [
  "flake8-bandit>=3.0.0",
  "flake8-black>=0.3.2",
]

Pants version is

2.10.0+gitb27a00dd

Hi, I just upgrade my pants to 2.10, and want to update my jvm BUILD files. My old BUILD file is like this:

jar_library(
    name='hadoop',
    jars=[
        jar('org.apache.hadoop', 'hadoop-client', 2.6.0),
    ],
    scope='compile',
)

How do I update it? What does

jar_library

change into now?