Hi Again everyone 🙂 I have a tiny question, I saw that on the previous version of pants there was goal named setup-py which (if I understand correctly) would generate the setup.py file. I understand that this feature is still available behind the scene when I see that the package is automatically created by pants. But, I would like to be able to use ‘pip install -e’ in order to develop my package, and for that I need to have a setup.py file for my package (it is a requirement from pip). Is it possible to write on the my file system the generated setup.py file ? Thanks for your answer 🙂 Arthur

Hello all, wondering if you would be interested in a contribution for

WSDL -> Java

backend? I have a working one implementation that Id be happy to share. Hopefully it’s less controversial than the Helm plugin we had a chat about already 😅

What's the best way to automatically depend on all

python_sources

below a certain BUILD file? I noticed that tailor isn't automatically creating a BUILD definition in the root of a package anymore?

Hi, I'm taking a whack at https://github.com/pantsbuild/pants/issues/13589 and it's beginning to feel like the wrong approach. In the issue one of the suggestions is to "avoid a proliferation of targets" which makes sense, but this really feels like it should be a separate item with:

download_file(name:str, description:Optional[str], url:str, expected_digest:str, expected_size:Optional[str], path:str)

That will then materialize the file to be used afterwards in any

file(s)

or

resource(s)

targets after the fact. Overloading

file

and

resource

with optional URL/digest/etc options feels more confusing than helpful

Hi there, I am having trouble with some tests and was wondering if anyone can guide me. My tests need files created at the start of the session and drop this test database on teardown. However, it looks like the files are not created (gridfs no file found). The same tests will succeed from the container (

docker exec -t projectA-container pytest tests projectA)

, which is one session. This is my current project structure:

projectA
  - tests
     - units
         - __init__.py
         - BUILD # tests
         - test_task1.py
     - utils
         - __init__.py
         - BUILD  
         - init_data.py
     __init__.py
     BUILD # test utils
     conftest.py

this is the relevant part of my

conftest.py

@pytest.fixture(scope="session", autouse=True)
def mongo():
    client = MongoClient(settings.MONGO_URI)
    db = client["test"]
    yield db
    client.drop_database("test")

I know that the tests are executed in parallel given enough cores so I was wondering if this could possibly affect the "session" scope? Any help to better understand this would be appreciated. Thanks so much!

For deprecated targets, is there any way to get tailor to rewrite them to the valid, newer target? For example

python_library

->

python_sources

Hi again Pants dev team! I have been meaning to drop back in again to share our experience and where we aim to go from here now that we have been setup on Pants for about a month and have successfully started disting projects from our repo. Unfortunately, for the moment I'm here for help as our builds have recently started failing on production CI servers (still works locally). The error is traced to when Pants tries to install its requirements packages from PyPI. Each attempt results in the following error:

18:30:01 SHA256 fingerprint of file:///var/tmp/pjenkslv/jenkins/workspace/casper-codetree-release-lib-ANY/casper/codetree/codetree/src/pantsbuild/pex verified.
18:30:01 Preparinng bootstrap with initial requirements
18:30:01 /ms/dist/python/PROJ/core/3.7.5/exec/bin/python: can't find '__main__' module in '/var/tmp/emmdev/.pex/unzipped_pexes/478cc1fa371ca40aa3e7dafee735ca438d4a243f'

The specific line is:

"${python}" "${pex_path}" --cert="${PIP_CERT}" -r requirements.txt -c virtualenv -o virtualenv.pex --retries=1 --timeout=1 --index-url="${PIP_INDEX_URL}"

The extra arguments are our own to make downloading packages work, but this is in the boostrap_virtualenv function, and it has worked fine until just recently. It's very hard to diagnose problems on the CI host, so at the moment I can't tell if this is Pants/Pex related or some problem with the host...

This is not immediately ringing any bells, but let's see

Hey all, I just wanted to write a quick appreciation message for a) Pants itself, and b) all the plugin help I've received here on Slack. I just finished re-writing the entire build/deployment process for a multi-year legacy project using Pants + some custom plugins, and I was able to gut a slapdash set of bash scripts, Dockerfiles, build containers, and who knows what else - in favour of a handful of BUILD files of like 15 lines of code each. I handed over the project today and this is essentially how it went: Me - "Okay, so to deploy, we have to generate the protobufs, cythonize our core libs, embed the protobufs and core libs in some of our sub-repos, Dockerize the API gateway and microservices, package our system services, and then deploy all of that to our server and then run e2e testing." Client - "Alright, this sounds painful, how do we do it?" Me - "`./pants deploy :myproject`" [drops keyboard and walks away]

I’ve got a 

pants-jupyter-plugin

 related question. I am using

pants-jupyter-plugin

  in AWS SageMaker Studio. I have a failure with

%pants_load

, but there is little information in the error log and I am struggling to investigate.

Hi 🙂 I got an issue with my module and my test. I’ve defined a python distribution like this :

resource(name="pyproject", source="pyproject.toml")

python_sources(name="source", sources=["./**/*.py", "!setup.py"])  

python_distribution(   
    name="utils",
    provides=python_artifact(
        name="utils",
        version="0.1.0",
    ),
    dependencies=[
        ":pyproject",
        ":source",
    ],
    wheel_config_settings={"--global-option": ["--python-tag", "py3"]},
)

But when I tried to run a test which is in another module, I got the following error :

ModuleNotFoundError: No module named 'utils'

I feel I’m not configuring as it should be, but I’m completely lost. Is there a project that I could have a look on to understand how to use pants ?

Hi, since we encounter a lot of issues, I would like to know if someone could provide us some consulting time in order to review our project and help us to figure out a working configuration ?

Just curious, what is the recommended way to have

skip_pylint

default to

False

for a project needing incremental adoption? I'd like to avoid having to create custom plugin overriding the skip default. I thought maybe macros can help but it seems a bit complicated for what we're trying to achieve.

📢 New blog post! Pants Contributor @wide-midnight-78598 introduces the PyOxidizer Pants Plugin that lands in the upcoming Pants v2.10. https://blog.pantsbuild.org/packaging-python-with-the-pyoxidizer-pants-plugin/

"Now I, at long last, have a fully integrated end-to-end Python workflow that starts with me typing code and ends with a fully tested executable binary."

📢 Pants v2.9 is featured in InfoWorld today! http://infoworld.com/article/3650508/a-brief-intro-to-the-pants-build-system.html

Hey Team, curious how we can pass along the credentials with a custom wheel repo: https://www.pantsbuild.org/v2.7/docs/python-third-party-dependencies#custom-repositories We use aws code artifact and provide the credentials in our poetry configuration.

Please join me in welcoming our newest Maintainer, @fresh-cat-90827! Alexey has made several meaningful contributions, including Yapf, blog posts, docs improvements, and being a really kind and welcoming community member. Thank you, Alexey! https://groups.google.com/g/pants-devel/c/dmGfHwK6Gfo/m/h04uIJ9aAQAJ

📢 Pants community newsletter issue 4 is out. It includes Pants in the news at InfoWorld; announcements; PyOxidizer integration preview by @wide-midnight-78598; plugin development tutorial also by SJ; how-to by @fresh-cat-90827 on choosing a Python interpreter for your Pants project; new maintainer @bitter-ability-32190; new contributors @nutritious-hair-72580and SJ, job openings at IBM, Orca, Rippling, and Nike; user stories; and more.

👋 pants team, I have a question around coverage-py: I’m running coverage through pytest (

[test].use_coverage = true

) on pants version

2.8.0

. I get an error when I try to run with these two configurations •

[coverage-py].global_report = true

in

pants.toml

•

[tool.coverage.run].branch = true

in

pyproject.toml

Everything works fine if one of these is set to

false

, but throws following error message if both are set to `true`:

ProcessExecutionFailure: Process 'Merge 2 Pytest coverage reports.' failed with exit code 1.
stdout:
Can't combine arc data with line data

stderr:

Pants is mentioned in the Software Engineering at Google book. An excellent reading in Chapter 18. Build Systems and Build Philosophy for anyone who deals with build systems like ourselves 🙂

Google has spent a tremendous amount of engineering effort over its lifetime in creating its own build system from the ground up, with the goal of ensuring that our engineers are able to quickly and reliably build code. The effort has been so successful that Blaze, the main component of the build system, has been reimplemented several different times by ex-Googlers who have left the company (2).

The URL in the footnote (2) https://www.pantsbuild.org/index.html which takes you to the web site (the page itself is not found though), but it’s taking you to the right site which is great!

Hey, guys. I’m trying out pants for our monorepo, and I’m having a lot of trouble figuring out how to get our Go project to build — was hoping someone here could give me some guidance.

tailor

generated a bunch of build files, but when I to run

./pants list ::

I get an error complaining that one of our dependencies does not exist — it’s something that we’ve vendored and linked through go.mod, and when I looked in the chroot for that step I found that only my mod and sum files were there. No sources or anything.

Was trying to get together the code for a potential

WSDL -> Java

codegen backend and I’m getting an import error when doing

./pants test src/python/pants/backend/codegen/soap::

on a fresh pull of the

pants

repo (well, in fact it happens when I try running any Python test using the

./pants

script). The error looks like the following:

_ ERROR collecting src/python/pants/backend/codegen/soap/target_types_test.py __
ImportError while importing test module '/private/var/folders/c9/5v4gbjh17w9_vy73fc90fnch0000gn/T/process-executionF88I01/src/python/pants/backend/codegen/soap/target_types_test.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/lib/python3.8/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
src/python/pants/backend/codegen/soap/target_types_test.py:9: in <module>
    from pants.backend.codegen.soap import target_types
src/python/pants/backend/codegen/soap/target_types.py:4: in <module>
    from pants.engine.rules import collect_rules, rule
src/python/pants/engine/rules.py:28: in <module>
    from pants.engine.engine_aware import SideEffecting
src/python/pants/engine/engine_aware.py:9: in <module>
    from pants.engine.internals import native_engine
E   ImportError: dlopen(/private/var/folders/c9/5v4gbjh17w9_vy73fc90fnch0000gn/T/process-executionF88I01/src/python/pants/engine/internals/native_engine.so, 0x0002): symbol not found in flat namespace '_PyObject_VectorcallMethod'

I did a

./cargo build

and

./cargo test

separately and those commands succeed … does any of know what I may be missing that causes that error?

I am wondering what is the best way to have certain projects in a Python monorepo declaring a different version of a 3rd party dependency when the root requirements have been resolved to a single constrains file.

Hello all, I am setting up a proof of concept Pants build for an existing small Python monorepo at work. First of all, thank you for this tool and for providing this forum for getting assistance! I have encountered a problem with (I think) a pytest dependency clashing with a project dependency, and I would appreciate any pointers you can give me on resolving it. In a nutshell, the project depends on version 21.4.0 of the attrs library, but an older version, 21.2.0, is pulled in as a pytest dependency (I think), and tests fail because they run with an incompatible mix of code from both versions. I am not sure if this indicates a bug in Pants or perhaps an error on my part. I'll dump details in the thread.

Export enthusiasts - is it possible to customize the output directory of "pants export ::"? It's currently written to dist/export/etc... , curious if it could be changed to e.g. just "env" to match what PyCharm does by default

Another export question - I noticed that the ./bin directory in the venv created by

pants export ::

does not have a "pip" file in it. Is that by design? My use case for it is using e.g.

pip list | more

as a quick test of what's in the venv for when I want to run something outside of running it via pants

OK, trying to pexify some legacy docker containers (with ensuing massive, massive reductions in container size and source code, which is all good...) ...but... having trouble with some namespace packages in the pex just... not existing. The pexes are built with

execution_mode="venv"

, but basically what's happening is that in my virtual environment I can import the namespace package and do a

dir

and see lots of stuff; the pex shows the identical dependencies in there, and I can still import the namespace package, but the result is an empty module. I can post more specifics, but is this a known thing with pexes that can be worked around?

Hey Pants Team, we're experimenting with docker builds on a M1 mac and we're experiencing an issue with running pants. We get a

killed

output with no additional info. We're trying to run with

--no-pantsd

and

--no-watch-filesystem

but no success just yet. Created this gist for logs.

Hey team, I am using M1 mac, trying to install pants and running into the following error:

./pants -ldebug version
Bootstrapping Pants using /Users/nizarhejazi/.pyenv/shims/python3.9
Creating the virtualenv PEX.
Downloading the Pex PEX.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   640  100   640    0     0   3023      0 --:--:-- --:--:-- --:--:--  3076
100 3529k  100 3529k    0     0  4661k      0 --:--:-- --:--:-- --:--:-- 4661k
SHA256 fingerprint of <https://github.com/pantsbuild/pex/releases/download/v2.1.42/pex> verified.
Failed to spawn a job for DistributionTarget(interpreter=PythonInterpreter('/Users/nizarhejazi/.pyenv/versions/3.9.5_x86/bin/python3.9', PythonIdentity('/Users/nizarhejazi/.pyenv/versions/3.9.5_x86/bin/python3.9', 'cp39', 'cp39', 'macosx_12_0_x86_64', (3, 9, 5)))): [Errno 2] No such file or directory: '/Users/nizarhejazi/.pex/venvs/d205c7f978b881f663df257d6bf11d02e6309c3b/832e95f85413646e8b7b056ab4e60414f83d7397/pex'
mv: rename /Users/nizarhejazi/.cache/pants/setup/bootstrap-Darwin-x86_64/pants.7jKJ9F/virtualenv.pex to /Users/nizarhejazi/.cache/pants/setup/bootstrap-Darwin-x86_64/virtualenv-20.4.7/virtualenv.pex: No such file or directory
Installing pantsbuild.pants==2.7.0 into a virtual environment at /Users/nizarhejazi/.cache/pants/setup/bootstrap-Darwin-x86_64/2.7.0_py39
/Users/nizarhejazi/.pyenv/versions/3.9.5_x86/bin/python3.9: can't open file '/Users/nizarhejazi/.cache/pants/setup/bootstrap-Darwin-x86_64/virtualenv-20.4.7/virtualenv.pex': [Errno 2] No such file or directory

I have been following this article to setup my env. I am running

./pants

command using iTerm w/ Rosetta. Any help is appreciated.

howdy friends 👋 is there any way to add excludes to jvm artifact resolution currently? I seem to be hitting an issue around coursier resolution of a specific transitive jar (the coursier json report is listing

"file": null

for it which the post processing script seems to be choking on)