I'd like to do a little poking around manually with contents of the application in my docker container. How could I start up an interactive python shell with the same python interpreter environment my pex app is using? I'm able to

exec

into a bash shell of my container, but not sure how to access the pex's interpreter that has all the third party dependencies I need.

Hey, With Python, I seem to be having a problem with importing trio when run from the

./pants run

command as well as in

./pants repl

. I'm running it on my local Ubuntu 22.04 machine where apparently the

sys.excepthook

is replaced by some

apport_excepthook

. Trio tries to deal with that, but needs to import

apport_python_hook

which seems to not exist in the pants environment. I'm wondering how the environment that the

./pants run

and

./pants repl

command are working in is set up. It seems to be somewhere between venv and running the system python natively as follows: • it is not able to import

apport_python_hook

which is available when running python3.10 on my system directly, but not in a venv. • when checking

sys.excepthook.__name__

that is set to

apport_excepthook

, same as when running python directly on the system, but not in venv.

Hey, Im trying to run pants 1.3 in a M1 Apple Silicon host running within a docker container of python 3.6.14-buster. Im getting a disconnect of the the Nailgun Server, before anything happens. Below is the stacktrace running

./pants --version --print-exception-stracktrace

Untitled.txt

Is this a known issue of running pants on a M1 Macbook?

Is there a convenient work-around? Im running the docker container by invoking

--platform linux/amd64

Running my pants version in an Intel version Mac, executes normally

We've posted on reddit's r/Python about Pants' recent adoption of multiple lockfiles. If you've had opportunity to explore this new feature, your comments/insights (or even just votes) there would no doubt be appreciated by curious Pythonistas. https://www.reddit.com/r/Python/comments/vc7i72/multiple_lockfiles_in_python_repos_a_hybrid/ And of course, as always, feedback is also much appreciated by the Pants team. Cheers!

hi was successful in getting pex file generated with 3rd party dependencies but getting this error due to proto buffer version. even after downgrading to 3.19 * version no sucess TypeError: Descriptors cannot not be created directly. If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0. If you cannot immediately regenerate your protos, some other possible workarounds are: 1. Downgrade the protobuf package to 3.20.x or lower. 2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower). More information: https://developers.google.com/protocol-buffers/docs/news/2022-05-06#python-updates

>>

[1]+ Stopped ./pipeline-pex.pex (venv) root@7781114-8501:~/pavithra/dagster-crawler-pipeline/dist# ./pipeline-pex.pex Python 3.8.10 (default, Mar 15 2022, 122208) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole)

>>

Hey, I'm having some python/architecture issues when running pants on an M1 machine. I'll post the stack trace in a thread

Hi, I am trying to find out whether editable installs as specified in PEP 660 or as supported by setuptools are supported by pants or how something similar can be achieved using pants.

Has any work gone into allowing Pants to build container images using Podman or Buildah to allow for rootless builds in CI environments?

Noticed some weird behavior with pants that I thought I would bring up. I have a messy monorepo, and after running

pants tailor

in the repo I ended up with a

BUILD

file in

.git/logs/refs/remotes/origin

. Contents of the

BUILD

file:

python_sources()

We have sort of a complex branch naming scheme, so I'm wondering if

pants tailor

saw a file in that directory that it thought was a python file and thus dumped a

BUILD

file in that directory? I'm wondering how

pants tailor

works its magic under the hood ...

Hey folks, I’ve recently implemented pants in a repo that uses gcp functions and aws lambda as targets. Everything is working beautifully 🎉 for package generation. The zip files are being uploaded using Terraform and here’s where I’m having issues - terraform always tries to redeploy the .zip files whenever that gets regenerated (or in a different machine or CI), seems like hash changes based on timestamp and not on source code changes only (which is the ideal). This likely isn’t a

pants

issue but maybe someone here has already solved for it 🤞 would the

terraform

backend for pants help me to only trigger

terraform apply

when need it?

Playing around with

v2.13.dev5

. Are there plans to let the

export

goal accept addresses to specific

python_requirements

targets? I saw in an example the use of

./pants export ::

but when trying to use a specific address it still resolves everything in

pants.toml

. Didn't see any documented args, so didn't try anything else to see if it's my own mistake (https://www.pantsbuild.org/v2.12/docs/reference-export)

So Pants is made up with a network of rules. Those rules are 'run' when we call

Get(Result, Request, data)

Pants assumes that

data

is immutable, and forces

data

to be hashable. This then allows Pants to memoise/cache calls to

Get

so no matter how many times

Get(Result, Request, 1)

is called, the rule will only ever get executed once. Oh and everything is async. How does Pants handle

MultiGet( Get(Result, Request, 1), Get(Result, Request 1) )

? Is this undefined behaviour? or can we still trust that the rule will only be ran once?

For my next "goal" with pants (pun intended 😉), I need to replace an old Makefile lint target that uses some ugly

find ... | xargs -0 cat | grep ...

commands to ensure that certain python modules do not import others. The purpose is to prevent circular dependencies, or to make sure that a client lib does not accidentally depend on server libs that don't get released. So, are there any pants goodies to help with circular dependency linting?

While I've personally never used it, I think someone made (or worked on) a plugin for

import-linter

https://github.com/pantsbuild/pants/issues/15247

This longstanding issue is relevant: https://github.com/pantsbuild/pants/issues/13393

Hey! fisrt question here:) i`m trying out Pants build for the first time on our existing monorepo, while i was able to work with most of pants features(and they are just perfect!) i`m still having hard time on understanding how to work with monorepo dependencies resolve and management, should i populate BUILD files with the dependencies manually? or should

./pants tailor

take care of that? i feel like i`m missing something here... Also, do you have any example for monorepo managed by pants build? I couldn't find anything more that basic setup online

Which is getting a PR soon!

I mean it's already in PR, lol

Hmm. That's backwards from how I was thinking about the import rules. It provides an allow-list approach, but I was thinking in terms of a disallow-list.

@proud-dentist-22844 Would

import-linter

(https://pypi.org/project/import-linter/) solve your problems? Curious if there is extra value in trying to get it running with pants, after the PR is merged

The contract modelling of

import-linter

sounds like just the thing, but I would rather have something that just reuses

pants

dependency graph instead of re-doing all of that work.

@proud-dentist-22844 PR is still open. Your voice matters 😉

Also @curved-television-6568 is totally a homie 😉

Hi! What you're missing (and presumably this is because we haven't documented this well enough, sorry) is dependency inference - Pants will automatically infer dependencies on both first and third-party code

The syntax will use specs, so a disallow list will be totally valid. Circular deps not so much though…