Hi! What are you trying to do with scm version?

I would like to dynamically have the git tag version as a version, as I did with poetry.

and I would like it to be the same for all the projects of my monorepo.

The upcoming Pants 2.13 release will have support for setuptools_scm (https://github.com/pypa/setuptools_scm/)

You can see an example of how it works here: https://github.com/benjyw/black/blob/pantsify3/src/BUILD

It's available in the 2.13.0a0 release from yesterday, for example

I'll try right away, thank you very much!

Ah ha! I forgot about

regex-lint

. That gave me a way to re-implement the current Makefile's (ugly) dependency linting while I wait for

visibility

to be available. 😄

Is there a mechanism to retrieve the list of source files in a target from a subset of members of that target? So, let's say I have 20 sources in a

swift_sources(name="mylib", sources=[...])

target, and my

check

goal gets the addresses:

helloswift/myfile1.swift:mylib

and

helloswift/myfile2.swift:mylib

- is there a request that will allow me to get all the other files in that target from those addresses? My current attempt feels yuckyish. Take all my addresses (from one or more

swift_sources

targets), get a single address per unique

target_name

, use `WrappedTarget`s and then using a

tgt.get(SourceField)

- feels like there must be a request somewhere which will take in a set of addresses and return unique targets (I originally thought this would be handled by

CoarsenedTarget

)

I'm trying to add

python_distribution

in the StackStorm repo... 😰 I've got the targets setup, a plugin to configure setup.py kwargs, and macros to reduce a bit more of the boilerplate. So far so good. But, I'm struggling with

dependencies

for the `python_distribution`s. In the old/manual setup.py (that I want to avoid because of so much copy paste, including copies of

dist_utils

functions... ick), it just used

packages=find_packages(exclude["setuptools", "tests"]),

to get the single package in that directory. Do people often have to add dependencies to all of the sub directories? I keep getting

NoOwnerError: No python_distribution target found to own

<some file or other that changes every time>. Is there a way to force pants to build incomplete wheels? I want to see what it has so far, but it seems I have to have all of the inter-dependent packages configured first.

Just guessing here now, but isn't there a no owners behavior option, like “ignore”?

Sounded plausible, but I couldn't find such an option.

Hmm.. you’re right. There doesn’t seem to be an escape hatch for this. I think this is the relevant docstring from the python backend rule `get_exporting_owner`:

“”"Find the exported target that owns the given target (and therefore exports it).

The owner of T (i.e., the exported target in whose artifact T’s code is published) is:

1. An exported target that depends on T (or is T itself).

2. Is T’s closest filesystem ancestor among those satisfying 1.

If there are multiple such exported targets at the same degree of ancestry, the ownership

is ambiguous and an error is raised. If there is no exported target that depends on T

and is its ancestor, then there is no owner and an error is raised.

“”"

Depending on where (in the python package namespace) this module is, perhaps you can “fake” the code be treated like a 3rdparty dep? (guessing that pulling the sources into the python dist in question is a no go)

By fake, I’m thinking about adding a python_requirement target for it, possibly with a module mapping to pick it up as such.

I just went through adding a bunch of directories to dependencies and finally got it to build. It feels so odd to do that though.

I shall force myself to go to bed now.

Oh, I know that feeling. 🛏️

Hey @happy-kitchen-89482 sorry for late response just got back from the weekend:) Thanks for the replies, i did took a second look at

dependency inference

docs but im still not quite sure i understand how to work with it.. I am referring to 3rd party dependencies, how are they being managed? should i manage a

requirements.txt

file manually? or perhaps should i manage the contents of BUILD files manually? What im trying to solve is the dependencies hell in our monorepo, i have never worked with other build tools like pants before and i feel like im missing something in the dependencies front

The python_distribution shouldn't typically need many dependencies. It does need explicit deps on its entry point(s), but all the transitive deps of those should be inferred.

So I'm curious as to why you needed to add many manual deps

These modules were not distributed as wheels before, so I have to figure out any missing metadata. The few entry points I have added should be injected into the python_distribution's setup kwargs by one of my plugins (the stevedore_extensions plugin) Then there are a series of scripts (not entry points) I need to register but I haven't looked up how to do that yet, or of pants even supports scripts (a top level kwarg for setup.py's setup -- each script is a file in the bin directory. Some are shell scripts and the rest are kebab-case python scripts.)

I see. Still, I think you should only have to manually add BUILD file deps on entry points, and everything else should be inferred.

(this is orthogonal to the setup kwargs)

Hi, I get

No valid Python interpreter found. For `pants_version = "2.11.0"`, Pants requires Python 3.7, 3.8, or 3.9 to run. Please check that a valid interpreter is installed and on your $PATH.

When will Python 3.10 be supported?

Is there any way to refer to pants targets relative to the current working directory? Coming from bazel, I'm used to doing things like

bazel run :myapp

to run the target named

myapp

in the current directory's

BUILD

file. It doesn't seem like that's possible with pants? I've only been able to successfully refer to targets with a fully-qualified name.

How do I define

scripts

for a

python_distribution

? https://python-packaging.readthedocs.io/en/latest/command-line-scripts.html#the-scripts-keyword-argument (scripts is not the same thing as entry_points as it can include bash scripts, or unimportable kebab-case python scripts) edit: moved from #plugins because this wasn't a plugin-development-related question

Any thoughts on using a different docker repository for a given registry? E.g. for registry A use

foo

but for registry B we want to use

ibm-foo

build_args.ARG_NAME

hmmmm

Lemme know if that doesn't work out. ;)