Hey all,

oh and does anyone know, how I can find out, which python imports to use in my monorepo? I'm debugging

could not import <http://some.path.in|some.path.in>.internal.library

Errors and would like to have something like "hey pants, list all the python import paths i could use in my monorepo"?

I just upgraded from Pants 2.7.1 to 2.8.0 and have a confusing failure when building a

pex_binary

(see thread)

Did any platforms support conversations already happened?

BUILD

go_binary(
    name = "bin",
)

docker_image(
    name = "image",
    dependencies = [":bin"],
)

Dockerfile

FROM alpine:3.11
ENTRYPOINT ["/bin/greeter_en"]
COPY cmd.greeter_en/bin /bin/greeter_en

on MacOS the image will have MacOS binary

We're running Pants in our CI. As suggested in the docs we have a cache that includes

.pants/named_caches/

and

.pants/lmdb_store/

. That cache grows a lot over time. On the first run the cache was about 1.5G. After just 5 or so runs it's now almost 3G. Any idea why it'd be growing so fast and we could do to keep it's size reasonable?

Hi! Is pants injecting some kind of env variable when it is instantiating pytest? I have a test suite that is spinning up a db as part of the test session setup - that can take a few seconds. When the tests run in independant processes, the db might get initialized on the same port despite some port check at start up. The way I was thinking to solve this is to get an int from pants that is different for each parallel test session so that I can increment the port to start the dynamic db on and get for example 17001 and 17002 at start up If people have been solving that differently I am open to other solutions 🙂

short of disabling inference alltogether, is there a way to partition off portions of code? Through whatever process, I've noticed that things like test util code and the likes are leaking into 'production' builds. I also spent a good 30minutes trying to work out why something wasn't working, and it was because my IDEs auto-import picked the wrong class to auto-import and pants just rolled with it.

Hello, I am a bit confused... I have the following setup: • source_root/org/project/main.py (and other files) • source_root/org/project/submodule_a/[some].py • source_root/org/project/submodule_b/[some].py main.py explicitly imports from both submodules, shouldn't I see them listed when I run

./pants dependencies source_root/org/project

?

Couple questions for pex_binary. (1) If your exec requires env setup (due to the nature of the hosts it is expected to run on), is a script entry point the preferred way of achieving this? If so, how do you direct it to run your module afterward (can it acquire the python exec/shebang and assume it’s in a relative root?). It seems none of the various PATH-like options in PEX docs are for this purpose. What about an equivalent shell “binary” built side-by-side that just invokes the PEX after env setup (could be better option as the shell binary can be used only when necessary). This is analogous to test and specify additional env vars before testing. (2) When specifying the output_path, is there any templating supported so you can get similarly generic output filenames but just specified to your liking (e.g., without src. prefix, or perhaps in a flat file structure where the dir name becomes part of the filenames)? (3) When specifying platforms, is there support for manylinux%YYYY%? We are targeting older REHL6 and REHL7 platforms (incidentally Pants only runs on REHL7 and so the default 3rd party dependencies it installs with pip are all manylinux2014+ and can’t run on REHL6–I know we can get fancier with the Python requirements/constraints/dependencies but that seems a lot harder than just saying the platform is X and hoping the build job pulls the right wheels). Thanks

Pants got covered in Computer Weekly! https://twitter.com/abridgwater/status/1463136043847274503

(monorepo) ➜  monorepo git:(main) ✗ ./pants dependencies ::          
16:43:13.00 [WARN] DEPRECATED: scope python-setup will be removed in version 2.10.0.dev0.

Use scope python instead (options: interpreter_constraints)
16:43:14.25 [INFO] Completed: Building dockerfile_parser.pex from dockerfile-parser_default_lockfile.txt
16:43:14.25 [ERROR] 1 Exception encountered:

  ProcessExecutionFailure: Process 'Building dockerfile_parser.pex from dockerfile-parser_default_lockfile.txt' failed with exit code 1.
stdout:

stderr:
ERROR: Exception:
Traceback (most recent call last):
  File "/home/marcelo/.cache/pants/named_caches/pex_root/venvs/s/53f402b6/venv/lib/python3.8/site-packages/pip/_vendor/resolvelib/resolvers.py", line 171, in _merge_into_criterion
    crit = self.state.criteria[name]
KeyError: 'dockerfile'

On 2.9.0.dev2 I'm having this /\

I seem to be getting this a lot lately - is there a way I can find out what’s causing it?

Is there a way to get fail-fast behavior when running python tests with pants?

I am trying to figure out how to port our django translations generation code to a pants-based build system. I assume the way I would need to do this is a codegen plugin? Is there a more straightforward way?

Is there anyway to set

--python-path

for the

pip

resolver job? I have a remote execution setup and want to allow devs to read but not write to the cache but is different on every system.

Hi, all 🙂 I am pretty new to pants. Currently we use pretty ugly shell scripts to build our python-images and tag them with a git-hash. Is there a way to do the same think with pants? Therefor, dynamically tagging docker_image-targets with some git/content state? Sry might be a very silly question..I already looked in the plugins section but I did not really know where to start.

My

python_library

depends on a

resource

that I'm hoping the

pex_binary

target will package correctly as a package resource during packaging. If my library reads this resource via

pkg_resources

tooling will my

python_test

target be able to call the library code that reads the package, or is the code under test not "packaged" at point of testing? This currently isn't working but I'm not sure if it's configuration a error or I'm expecting this to work when it's not going to

13:44:26.59 [WARN] DEPRECATED: scope python-setup will be removed in version 2.10.0.dev0.

What should I use as replacement? 🤔

@hundreds-father-404 Is the

OverridesField

meant to always be subclassed?

If you work with Python, please participate in this. We at Pants team know how invaluable community survey responses are for guiding an open source project to make good choices.

Just giving you all a heads up that the Python Developers Survey will be wrapping up in the coming week. 

  https://surveys.jetbrains.com/s3/python-developers-survey-2021

The more diverse our response base is, the better so help us share the link this week as well to your regional communities. The survey takes about 10-15 minutes to fill out.

Ewa Jodlowska

Executive Director

Python Software Foundation

ewa@python.org

What is the downside of setting PANTS_CONCURRENT=True? This is coming up for our team because we often have a pants command running (list tests) while also trying to commit code (which uses pants for pre-commit hooks). Allowing concurrent runs would unblock this pattern, but I can't figure out what would break.

Hi everyone, I'm facing some issue with pants building the lambda. It was working fine previously but suddenly got stuck and doesn't seem to work from then on. I have tried restarting pantsd, clearing pants cache and restarting my computer as well. Attached are the screenshot, debug logs and pex verbose logs. cc @faint-businessperson-86903 Would appreciate any help in debugging this !

A poll, votes and comments appreciated! Right now you write test timeouts like this:

python_tests(timeout=120)

Should the value instead be like this?

"120s"
"10s"
"2m"
"1.5m"

A for the status quo, B for setting the time unit Update going to accept both styles to avoid breaking BUILD files

Hello Pants community, first time poster here! My team and I currently have 2 problems after switching to pants as our monorepo-everything-tool. Hope you can help us shed some light on our issues!

pants 2.7.2

python 3.8.10

poetry

1. Pathing on a new instance. mlm_training.py can't find dsutils under libs (see folder and our setup script below) 2. Dependency resolving with poetry - We have an issue where we have 2 different projects that use scikit-learn [0.23.1, 1.0.1]. - In each project folder we have pyproject.toml specifying this. - Pants either 1. ignores one of the versions or 2. if specified as a dependency in BUILD (for both projects) returns the message "could not resolve constraints" data-science | ├── libs │ |__dsutils │ ├── BUILD │ ├── clean.py │ ├── config.py │ ├── data.py │ ├── init.py │ ├── path.py │ ├── pyproject.toml │ ├── README.md │ ├── tests │ │ ├── test_clean.py │ │ ├── test_path.py │ │ └── test_tokenizer.py │ ├── tokenizer.py │ └── utils.py ├── projects │ |__language_model │ ├── BUILD │ ├── config.py │ ├── data │ ├── data.dvc │ ├── init.py │ ├── mlm_training.py │ ├── models │ ├── models.dvc │ ├── params.yaml │ ├── pyproject.toml │ ├── README.md │ └── utils.py ├── constraints.txt ├── mypy.ini ├── pants ├── pants.ci.toml ├── pants.toml ├── pyproject.toml ├── README.md Relevant contents of

pants.toml

[source]
root_patterns = [
  '/libs',
  '/projects',
]

Contents of relevant

setup.sh

script (some steps before this):

echo "Installing pip"
"${PIP}" install pip --upgrade
echo "Installing poetry"
"${PIP}" install poetry
# Install all our requirements.txt, and also any 3rdparty
# dependencies specified outside requirements.txt, e.g. via a
# handwritten python_requirement_library target.
echo "Poetry update"
poetry update
echo "Installing dependencies"
"${PIP}" install -r <(poetry export --dev --without-hashes) -r <(./pants dependencies --type=3rdparty ::)
echo "Remove lockfile"
rm poetry.lock
echo "Generating constraints.txt"
rm constraints.txt
pip uninstall pkg-resources==0.0.0 -y # Have tried commenting this out.
pip list --format freeze  >> constraints.txt

hi, not sure if this is the intended behaviour... when i run

./pants check my.package::

where

my.package

depends on

other.package

and

other.package

is in the same repo it pulls in the correct version of

other.package

otoh, when i run

./pants check ::

it seems to use the version of

other.package

on the filesystem - ie doesnt respect any specified versions or pull in the last published from pypi

I'm having a hard time creating the setup for

./pants publish

with

twine

🤔 does someone have an example?

These docs are not published yet, but perhaps provide enough insight to nudge you in the right direction ? https://www.pantsbuild.org/v2.9/docs/python-publish-goal

If not, I’m happy to assist, so plz just ask 🙂

ah, this is what I wanted

thanks