What do folks think about the need for an additional task framework (e.g. Invoke, Rake, Make, etc.) in repositories managed via Pants? Do you use a task framework for custom tasks, or do you bake them into Pants via plugins?

@helpful-lunch-92084 won't be removed till 2.5. 2.4 only changes the default

ah cool

https://twitter.com/cczona/status/1366520316336377858 Pants Build retweeted: I'm looking for a few popular Python apps, built with Django or Flask, that have above-average test suites. Recommendations please! Twitter

If you're interested in build tools more generally, Google is giving several talks this Thursday about their Bazel project https://opensourcelive.withgoogle.com/events/bazel

If you’re interested in Pants doing something akin to Bazel Day (on a smaller scale than Google’s), please say aye. It’d be great to hear what topics or cases would most interest you personally. If there’s enough interest, it can be made to happen.

Hi all 👋 Recently found out about the promising looking pants project. excited So far, I've come across one thing that I'm sure there is a good explanation to why it needs to be the way it is, but I can't help feeling it is an itch, that I might need to scratch, if it all possible (without too much effort.) and that is the module_mapping of python requirements. Introduced by this PR: https://github.com/pantsbuild/pants/pull/10025 The thing is, as I'm sure you know already, that the mapping we input here, is already available information from the packages themselves from the top_level.txt file once installed. Can't we use this information from the source, instead of having to manually provide it?

Hello, everyone... I'm in the process of adding Pulumi to our project (https://www.pulumi.com), and using the Python SDK for it. The

pulumi

CLI is a Go binary, but to execute our infrastructure program written in Python, it needs to be invoked from inside a virtualenv with the right dependencies. Is there some kind of way for Pants to create such an environment for me, and then "get out of my way" and let me execute arbitrary

pulumi

commands in that environment? I see there's a

pants run

command, but that looks like it's for executing Pex binaries. Can that be adapted for my usecase, or is there another way? Thanks 🙇

I'm kind of baffled by this error here:

Exception: Unmatched glob from the option `--python-setup-requirement-constraints`: "constraints.txt"

Huh, shouldn't

/build-support/virtualenvs/

be in our

.gitignore

?

no, run

git clean -fd -- build-support

. Stu made a change to move the venv

Right, just found #11616

I got caught straddling that change

Is there an easy way to get the sources of a target via pants command line?

We just put on a new pair today and merged the upgrade from v1.25 to v2.2 into master! Thanks again for all your help along the way. I imagine the coming days will surface a few things that we missed that the developers encounter but 🙏

hey, is there a way to store the python_distribution version argument in a file? in most python libraries one can do

import x

x.___version___

and i was thinking of not duplicating that information (existing setup.py-s were reading the version number from a module file)?

./pants package my_lib::

with no setup_py_commands exports the "versioning" file but I'm not sure how to make python_distribution read from it

hello! after a little break to fight fires I'm back to switching our tooling over to pants 🙂 Something I've noticed is that running individual test files appears to take roughly twice as long with pants as opposed to just running them with straight pytest: (I ran this twice in a row so all the build steps would be cached and it's only spending time running the actual tests)

(remit) [nate@ragin-cajun remit-srv]$ time ./pants test --force tests
Scrubbed PYTHONPATH=/home/nate/wave/remit-srv/src: from the environment.
09:56:24.43 [INFO] Completed: test - tests/test_terrapay.py succeeded.

✓ tests/test_terrapay.py succeeded.

real	2m23.628s
user	0m0.429s
sys	0m0.042s

compared with:

(remit) [nate@ragin-cajun remit-srv]$ time pytest tests/test_terrapay.py
============================================== test session starts ==============================================
platform linux -- Python 3.8.5, pytest-6.0.1, py-1.9.0, pluggy-0.13.1
rootdir: /home/nate/wave/remit-srv
plugins: celery-4.4.7, requests-mock-1.8.0, Faker-4.1.1, cov-2.10.1
collected 596 items

tests/test_terrapay.py .................................................................................. [ 13%]
......................................................................................................... [ 31%]
......................................................................................................... [ 48%]
......................................................................................................... [ 66%]
......................................................................................................... [ 84%]
..............................................................................................            [100%]

======================================== 596 passed in 67.94s (0:01:07) =========================================

real	1m13.382s
user	0m59.747s
sys	0m2.068s

I'm just a little confused to how to start debugging this or how to figure out what's going on that's causing the discrepency

A number of OSS projects/orgs offer community open office hours. Some offer time slots for 1:1, some offer 1:Many or Many:Many formats, for example: https://twitter.com/chrisalbon/status/1367536299876360194 If folks are interested in volunteering to do any type, I'd be happy to do the logistical setup for you, so a person can pretty much just show up for 20-60 minutes of contributing whatever your Pants experience is, and voila done. It'd be valuable to, for instance, do a casual demo of how your team is using Pants or a problem it's helped you solved. Who's interested in possibly teaming up?

https://twitter.com/cczona/status/1367928332419932160 Pants Build retweeted: Proud member of @ThePSF here! Membership drive is going on right now. PSF does so much important work. Membership i… https://twitter.com/i/web/status/1367928332419932160 Twitter Happy Anniversary to Python and the PSF! Python is 30 & the PSF is 20 years old this year! Your support is what mak… https://twitter.com/i/web/status/1367487264251592713 Twitter

I thought we had, a while back, fixed the problem of not invalidating the build graph when a

requirements.txt

changes? By injecting a dep on the file? I seem to be having an issue.

https://twitter.com/rust_foundation/status/1368280635513712641 Pants Build retweeted: 💯💯💯 "A programming language [gets] better through more, not less, diversity in perspectives." "Popular programming… https://twitter.com/i/web/status/1368280635513712641 Twitter

just ran into this on 2.2, we were trying to do a

pants run path/to/binary -- binary’s arguments

. Now the binary’s arguments happened to have brackets

[]

in them and pants was aborting with:

File "/Users/nate/.cache/pants/setup/bootstrap-Darwin-x86_64/2.2.0_py38/lib/python3.8/site-packages/pants/util/eval.py", line 47, in parse_expression
    raise raise_type(
pants.option.errors.ParseError: The value cannot be evaluated as a literal expression: SyntaxError('unexpected EOF while parsing', ('<string>', 1, 8, '[test] quoting'))
Given raw value:
1: [test] quoting

In v1 we made heavy use of pants run with

--

expecting pants to stop processing argv after that. I tried looking at

--run-args

but it seems that the brackets still cause it to bail.

Hello! I am having some troubles with the

files

target in Pants v2.X I have the following files (see screenshot), as well as the following BUILD file:

python_library(
    name='test-handler',
    sources=[
        'lambda_handler/test.py',
        ':test-queries'
    ],
    dependencies=[],
)

python_awslambda(
    name='test-lambda',
    dependencies=[
        ':test-handler',
    ],
    runtime='python3.8',
    handler='test.lambda_handler.test:handler',
    output_path='lambda/test/test.zip'
)

pex_binary(
    name='test-pex',
    dependencies=[
        ':test-handler',
    ],
    entry_point='test.lambda_handler.test:handler',
    output_path='lambda/test/test-pex.zip'
)

files(
    name='test-queries',
    sources=[
        'queries/test.sql'
    ]
)

The objective is to include some SQL files in an AWS lambda target. However, when I unzip the final artefacts, the SQL files are not included (as shown by the screenshot). We started having this issue since the migration from 1.30 to 2.0. How can I include files in an AWS lambda target?

one of our devs is on mac 11.2 and is getting the following bash error when running pants tests:

fallible_to_exec_result_or_raise
    raise ProcessExecutionFailure(
pants.engine.process.ProcessExecutionFailure: Process 'Searching for `bash` on PATH=/usr/bin:/bin:/usr/local/bin' failed with exit code -9.
stdout:

I’ve verified that he indeed does have bash installed:

$ which bash
/bin/bash

Curiously this is what he sees when executing /usr/bin/env bash

$ /usr/bin/env bash
The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit <https://support.apple.com/kb/HT208050>.
bash-3.2$

However it appears that it is indeed a bash shell he’s entered into unless Mac 11.2 is doing something funky. Has anyone ran into this?

Working through adding windows support for pex. It seems to be a common theme that one of the most pervasive issues is the location of the python executable. One of the specific location issues I am focusing on now is the hashbang that seems to be every where 

#!/usr/bin/env python

 something that will never resolve in windows.  It's even part of the tl/dr ! https://pex.readthedocs.io/en/latest/whatispex.html#tl-dr That raises some questions:   For window support would we be willing to (just for windows users) drop the idea of being able to execute a .pex file alone. Example: https://github.com/pantsbuild/pex/blob/master/tests/tools/commands/test_venv.py#L533 changing to 

subprocess.check_call(args=[sys.executable, "-mpex", pex_file, "venv", venv], env=make_env(PEX_TOOLS=1))

And then in general, are we ready to have different paths in a few places the code base with a few 

if WINDOWS

 statements that will be required to achieve first party support for windows?

https://twitter.com/stuhood/status/1369413790392066048 Pants Build retweeted: "Helping dad make distributed builds even easier!" Twitter

Pants onesie! 👖 💕

We don't have a way to explicitly depend on everything in a

requirements.txt

do we?