Yes.

./pants --no-pantsd jupyter  3rdparty/python:boto3

does not work

But that is not a game stopper.

@jolly-midnight-72759 how to get third party dependencies working:

@jolly-midnight-72759 how to handle Python 2 vs. Python 3.

Is

from pants.base.build_environment import get_buildroot

a Pants™ approved way of getting the root of the monorepo in a plugin?

whow. I just had an idea on how the Jupyter Lab version of this plugin should work.

Hopefully @jolly-midnight-72759 @damp-quill-59187 no one will deal with the same confusing error message you both had, after this PR. https://github.com/pantsbuild/pants/pull/11081 Feedback appreciated on the PR description about the wording of the new error message!

Happy to announce that our Jupyter Notebook plugin is now working! * launches a jupyter notebook app (older version as of today) * adds targets to the

PYTHONPATH

for the app * automatically picks the appropriate python interpreter * sets the dashboard homepage to the top of the repo Next improvement: allow for different Jupyter Notebook versions depending on if PY2 or PY3 was chosen. https://gist.github.com/rcuza/bbcf8f5a13964db7760ff376649c1a44 Big thank you to @hundreds-father-404 and everyone else who helped out.

Here's a snapshot of my docker plugin so far. It supports building, tagging, retagging, and pushing images to a repository (usually via retagging). The source needs to be cleaned up a bit and I need docs and tests added, but it's working well for me in CI and publishing packages to our internal artifactory regularly. I have things set up so running these commands do sort of what you'd expect:

./pants package --docker-image-tag="${BUILD_TAG}" $targets
./pants publish --registry=<http://my-docker-registry.company.com:5000|my-docker-registry.company.com:5000> --image-tag="${BUILD_TAG}" $targets

Big thanks to @hundreds-father-404 for the help and patience as I learned the rules API

I'm trying to add a new target type that can download files and use them as

files

-like dependencies...i get how to create the target type, but what kind of object do i need to return in my rule to make it available as a dependency of other targets?

GeneratedSources

maybe?

How would I go about installing poetry using Pants plugins if it uses a python file to work?

is there an easy way to search for targets whose addresses match a certain patter in the rule api?

how do I rename a file in a

Digest

? I see

AddPrefix

and

RemovePrefix

for adding and removing directory prefixes but nothing to change the filename of a file in a

Digest

.

Riffing off of @fast-nail-55400 question ☝🏽, but not wanting to hijack thread: will this proposed

FileDigest

handle different file types, like symbolic links, sockets, etc or just text and binary files? I don't see a reason why it would, but if you do, then whatever the solution should be able to intuitively encompass filesytem api's.

E       Exception: No installed QueryRules can compute WrappedTarget given input Params(str), but it can be produced using:
E         Params(Address)

I already have

QueryRule(WrappedTarget, (Address,)),

in the

RuleRunner

setup and my code goes from

Address

to

WrappedTarget

, unclear where

Params(str)

is coming from, maybe not my plugin’s rules?

Trying to write a test for a goal_rule, the rule uses the workspace.write_digest(...) api, I want to be able to pass a tmpdir to it so the test writes the files the rule generate to a know temporary location (tmpdir is a fixture provided by pytest). However, it seems that Workspace.write_digest expects a relative path, which makes sense in non-test scenarios, but probably a bad idea to write stuff to places under the chroot when running a test. I have looked at https://www.pantsbuild.org/v2.2/docs/rules-api-testing#testing-goal_rules but I haven't found any docs/tips about having workspace.write_digest() run and asserting on the result of that. Any ideas/workarounds ?

Hello everyone, I am trying to write a plugin that will dynamically generate the version number

from pants.backend.python.goals.setup_py import SetupKwargsRequest
from pants.engine.target import Target

from pants.engine.rules import collect_rules
from pants.engine.unions import UnionRule
from pants.backend.python.goals.setup_py import SetupKwargs
from pants.engine.rules import rule

class CustomSetupKwargsRequest(SetupKwargsRequest):
    @classmethod
    def is_applicable(cls, _: Target) -> bool:
        return True

@rule
async def setup_kwargs_plugin(request: CustomSetupKwargsRequest) -> SetupKwargs:
    return SetupKwargs(
        {**request.explicit_kwargs, "version": "1.4"}, address=request.target.address
    )


def rules():
    return [
        *collect_rules(),
        UnionRule(SetupKwargsRequest, CustomSetupKwargsRequest),
    ]

And my BUILD file looks like this:

python_distribution(
.....
	provides=setup_py(
			name="testapp",
            version="1.0.3",
		),
	setup_py_commands=["sdist", "bdist_wheel"]
)

If I try to remove the version="1.0.3" - it complains Missing a

version

kwarg in the

provides

Am I missing anything?

Does AsyncFieldMixin serve a purpose any longer? It looks like the pratical upshot is it stores Address parameter required in the Field constructor whereas a bare Field just throws that parameter away after using it to compute the field value; IOW Field uses less memory than AsyncFieldMixin, but that is all.

Hi, I have some question. Is it possible to have two

requirements.txt

files in separated folders for separated packages and with the same dependency (3rd part)? Because when I want to add the same dependency in second

requirements.txt

I lose the first one. I saw in docs

Dependency inference will no-op if >2 targets refer to the same file

section.

sorry wrong channel

In v2.2.0 is this still correct?

[GLOBAL]
pythonpath = ["%(buildroot)s/pants-plugins"]

I've been trying to follow the docs on how to create a plugin and not having any luck.  So far I have this in pants.toml

[GLOBAL]

pants_version = "2.1.1"

pythonpath = ["%(buildroot)s/plugins"]

backend_packages = [

"pants.backend.python",

"dash_app",

]

[source]

root_patterns = [

"plugins",

]

 I have the follow directory structure in the repo:

plugins

BUILD

register.py

dash_app

BUILD

dash_app.py

Can I trigger goals from within my plugin? For example, I'm building a custom package goal and need to trigger the normal package goal on some targets first.

Currently we can eagerly validate fields during BUILD file parsing by overriding

Field.compute_value

but we cannot do said same for a

Target

as a whole. This precludes validating cross-field data until rule execution time and possibly means needing to complicate rule structure in order to DRY up this validation when the validation is in fact universal. A classic example would be mutually exclusive fields but I imagine there are other cases as well. Id there any reason not to introduce a

validate

hook method on

Target

called at the end of initialization that could be overridden to provide validation?

if i wanted to integrate boto3 with a plugin, is there a correct way to do that that fits into the plugin execution model? it doesn't seem like multithreaded blocking APIs fit will into the curent rule API

Hi all! 👋 I’m new here and I’m just starting exploring Pants. 😄 @hundreds-father-404 encouraged me to ask on this channel and hear your thoughts. So, in my team, we use Makefile command (

make deb

) to build a Debian package based on the Dockerfile like it was described in this blog post. I would like to use Pants (probably

./pants package

goal?) instead Makefile command to build a Debian package. My initial thought was to use Pants Docker plugin. There are two plugins: • implemented by @magnificent-hamburger-46133 (works for Pants v1) - stored here, • implemented by @flat-zoo-31952 (working for Pants v2) - discussed here. Is it a good way of thinking or is there a better approach to solve it? Here is the example repository with my problem. Thanks in advance for your opinions! 🙇‍♂️

🧵 having an issue with the a custom plugin. details in thread

Has anyone here done any work with using Pants to manage infrastructure related projects? In particular I'm working on a repository that's got a bunch of PyInfra (pyinfra.com) code, and I want to be able to use Pants to manage it. This includes using Packer as the build tool to launch a host, configure it with the associated pyinfra package, and then execute a suite of testinfra tests against it. I'm also thinking of looking at collecting the test results from the build/test runs for managing longitudinal reporting.

I'm trying to strip the source roots of files that have source roots, however cause I'm using python_requirements() my requirements.txt file is added as a PythonRequirementsFileSources, and when I try to get

StrippedFileSources

it complains:

09:12:58.88 [ERROR] Exception caught: (pants.engine.internals.scheduler.ExecutionError)
  File "/Users/nate/.cache/pants/setup/bootstrap-Darwin-x86_64/2.3.0rc1_py38/lib/python3.8/site-packages/pants/bin/local_pants_runner.py", line 246, in run
    engine_result = self._perform_run(goals)
  File "/Users/nate/.cache/pants/setup/bootstrap-Darwin-x86_64/2.3.0rc1_py38/lib/python3.8/site-packages/pants/bin/local_pants_runner.py", line 167, in _perform_run
    return self._perform_run_body(goals, poll=False)
  File "/Users/nate/.cache/pants/setup/bootstrap-Darwin-x86_64/2.3.0rc1_py38/lib/python3.8/site-packages/pants/bin/local_pants_runner.py", line 184, in _perform_run_body
    return self.graph_session.run_goal_rules(
  File "/Users/nate/.cache/pants/setup/bootstrap-Darwin-x86_64/2.3.0rc1_py38/lib/python3.8/site-packages/pants/init/engine_initializer.py", line 130, in run_goal_rules
    exit_code = self.scheduler_session.run_goal_rule(
  File "/Users/nate/.cache/pants/setup/bootstrap-Darwin-x86_64/2.3.0rc1_py38/lib/python3.8/site-packages/pants/engine/internals/scheduler.py", line 568, in run_goal_rule
    self._raise_on_error([t for _, t in throws])
  File "/Users/nate/.cache/pants/setup/bootstrap-Darwin-x86_64/2.3.0rc1_py38/lib/python3.8/site-packages/pants/engine/internals/scheduler.py", line 536, in _raise_on_error
    raise ExecutionError(

Exception message: 1 Exception encountered:

  NoSourceRootError: No source root found for `requirements.txt`. See <https://www.pantsbuild.org/v2.3/docs/source-roots> for how to define source roots.

When I get the regular merged SourceFiles however, there is nothing in the

unrooted

tuple? which seems to be how I would want to detect if a particular file is in a source root or not?

set the channel description: Help with writing Pants Build System plugins.