I see that the docs for 1.27 have a section on constraint files and the release notes for 1.26 mention adding the ability to use python lockfiles. Are there any differences in how lockfiles are used between 1.26 and 1.27 or am I safe using the docs for 1.27? 1.27 doc: https://www.pantsbuild.org/v1.27/docs/python-third-party-dependencies 1.26 release notes: https://www.pantsbuild.org/v1.27/docs/release-notes-1-26

Looks like when running a PEX I can access environment variables. Wondering if there is a way to have pants add variables to the environment when running a PEX. Also wondering if it can be done in a way that is user specific. Something like how gradle handles local.properties. The specific use case I'm thinking of is when there is a utility that requires sensitive information. Perhaps a utility that requires a username and password. Only certain users should have the credentials and they shouldn't be added to source control. Users with access might have something like a .pants file containing the environment variables, which is ignored by git. Anything like this exist?

Hello again. I am trying to convert my “python_app” targets to “archive” targets and im running into this error.

15:08:58.38 [ERROR] Exception caught: (pants.engine.internals.scheduler.ExecutionError)
  File "/Users/briandesimone/.cache/pants/setup/bootstrap-Darwin-x86_64/2.1.1_py36/lib/python3.6/site-packages/pants/bin/local_pants_runner.py", line 255, in run
    engine_result = self._run_v2(goals)
  File "/Users/briandesimone/.cache/pants/setup/bootstrap-Darwin-x86_64/2.1.1_py36/lib/python3.6/site-packages/pants/bin/local_pants_runner.py", line 182, in _run_v2
    return self._maybe_run_v2_body(goals, poll=False)
  File "/Users/briandesimone/.cache/pants/setup/bootstrap-Darwin-x86_64/2.1.1_py36/lib/python3.6/site-packages/pants/bin/local_pants_runner.py", line 204, in _maybe_run_v2_body
    poll_delay=(0.1 if poll else None),
  File "/Users/briandesimone/.cache/pants/setup/bootstrap-Darwin-x86_64/2.1.1_py36/lib/python3.6/site-packages/pants/init/engine_initializer.py", line 126, in run_goal_rules
    goal_product, params, poll=poll, poll_delay=poll_delay
  File "/Users/briandesimone/.cache/pants/setup/bootstrap-Darwin-x86_64/2.1.1_py36/lib/python3.6/site-packages/pants/engine/internals/scheduler.py", line 569, in run_goal_rule
    self._raise_on_error([t for _, t in throws])
  File "/Users/briandesimone/.cache/pants/setup/bootstrap-Darwin-x86_64/2.1.1_py36/lib/python3.6/site-packages/pants/engine/internals/scheduler.py", line 539, in _raise_on_error
    wrapped_exceptions=tuple(t.exc for t in throws),

Exception message: 1 Exception encountered:

  ProcessExecutionFailure: Process 'Create db.data_cache_db.lexio-migrations-data-cache.tar' failed with exit code 1.
stdout:

stderr:
Usage:
  List:    tar -tf <archive-filename>
  Extract: tar -xf <archive-filename>
  Create:  tar -cf <archive-filename> [filenames...]
  Help:    tar --help

This doesn’t give me much to go on here and even with debug mode on this is the extent of the error message. Here is my BUILD file:

python_library(
    name="lib",
    dependencies=[
        "3rdparty/python:alembic",
        "3rdparty/python:SQLAlchemy",
        "lib/python_core/src",
    ],
    sources=["**/*.py"],
    tags={"code", "db", "migration", "python"},
)
pex_binary(
    name="alembic", entry_point="alembic.config", dependencies=[":lib"], zip_safe=False
)
archive(
    name="lexio-migrations-data-cache",
    packages=[":alembic"],
    files=[":files"],
    format="tar",
    tags={"code", "db", "migration", "python"},
    output_path="db.data_cache_db.lexio-migrations-data-cache.tar",
)
files(
  name="files",
  sources=[
    "alembic.ini",
    "env.py",
    "versions/*.py",
  ],
)

Any help here would be appreciated

👋 happy new year folks.

curious is anyone has any thoughts, ideas or prior art on pip-orchestrated composition of pypi distributions + monorepo-materialized distributions in off-the-shelf virtualenv environments? we seem to be butting our heads against this in the ML/DS space and I have a few ideas that I wanted to discuss w/ likeminded folks.

Is there a repo or collection of externally maintained or unofficial modules for pants? I'd really like to get my hands on a Docker + Kubernetes plugin.

@gorgeous-eve-12553 We have been using those that we upgraded internally to make it work with 1.30 https://github.com/toddgardner/pants-plugins

Has someone faced

'PrimitiveField' object has no attribute 'filespec'

it looks like some of our plugins are breaking the pants intellij import

Not sure what that means though everything else is working properly

1.30 pants

Hi! I am really impressed with the pants2 build system 😄 I am trying to write my first plugin. But I have some code written with 3.8 syntax (walrus operator). How do I change it so the plugin runs with python 3.8? Currently, I tried `python_library(interpreter_constraints=["==3.8.6"])`in BUILD in the same file as the plugin sources. But it didn't work. I am using

pants_version = "2.1.1"

Hello everyone. Just want to say Pants is great. I've been using it for over 3 years now on all of my Java projects! It's the best build system I know of. Thanks for all your work.

Hey! Seeing the end of the tunnel to get all our platform on pants 1.30 🎉 . Right now trying to figure out a strategy for versioning. I was thinking having a python function that would be available in all BUILD files to be able to get the version or a commit hash. I was looking in the plugins docs and that explains targets and tasks but it doesn't feel like that would fit in there. Thank you

you can use a BUILD macro to inject a version

macros cannot read files, but if you’re ok editing the macro definition to bump a version…

commit hash is slightly more challenging right now, although possible. would need more details about which BUILD symbols need to consume it.

the commit hash would be for the docker tags, feels like I could customize the plugin itself since I have that already

we would want every image to be tagged twice

with the commit hash

and the propective version

and at release just tag the release on it

the challenge with doing it via a plugin is effectively: https://github.com/pantsbuild/pants/issues/7022

Does this mean that I could build an arbitrary function in a macro but it just needs to be a pure python function (no external dependencies)?

yea, a pure function would be safe

the challenge is that interacting with git would violate that

Hum - what strategies have you guys seen in the past?

I am also thinking of the python lib publish function we will need to be able to inject something in there

there are better facilities for this in v2 (uncacheable rules, passing things as options, etc), but in v1, the surest defense is to very lazily apply

😛

if you have a v1 Task, wait until you are running the Task to choose the version, and run the logic there… ie, don’t do it in your BUILD file